Use Ctrl+F on your keyboard to search for a term inside the page!
Two basic checks : is your PHP version > 5.1 ? On some shared hosts, you must activate PHP5 in a given folder by setting an .htaccess instruction. Refer to your host documentation. Second question (particularly on Linux installations ) is dom-xml extension enabled for PHP? If not, update and install (via yum or equivalent) the php-xml package, and everything should work fine.
Change the error_reporting level of PHP to not display the E_NOTICE errors.
This can be done either by setting a php_value inside an .htaccess file at the root of your installation, or more simply by modifying directly the php.ini file of your server. A typical « production » value recommended by the PHP team is error_reporting = E_ALL &~E_NOTICE
You may ask yourself why do such errors appear?! These errors are more warnings than errors and do not prevent the application from functioning. AjaXplorer is mostly a single-man long term work and began when PHP was one or two versions from here, and some low-level language structure have changed since them, even if still supported. So be indulgent and disable E_NOTICE ok?
As for 3.2.1, there is now an optimization cache that keeps track of the full plugins registry. You’ll have to simply delete the two files plugins_requires.ser and plugins_cache.ser located either in server/conf/(until 3.2.4) or in data/cache (after) and refresh your browser to regenerate them. The registry should be up-to-date.
For developers, you can even disable this cache totally by using the AJXP_SKIP_CACHE variable inside data/conf/bootstrap_context.php.
You may have charset problems that have been stored inside the user’s preferences, and each time you try to log in, they are sent to the browser and trigger an application error. It’s not normal, and you should try to find out what went wrong, but a basic action can be to clear the user’s preferences : if you are using the default conf.serial driver, go to data/plugins/conf.serial/[username]/ and remove both prefs.ser and bookmarks.ser, this can sometimes help!
File upload size limit is not an AjaXplorer limitation, but a server configuration for PHP. If on a shared host, it is unlikely that you can access this configuration. If you are on your own server and can edit the PHP configuration file (php.ini), please have a look at the upload_max_filesize instruction on the PHP website.
This often happens if you have created a repository but not granted access to this repository for each user. Logged in as admin, open the Settings repository, Users Management tab, and give read/write access to the newly created repository to whichever user you want.
Most distributions do not set the locale used by the server filesystem in webserver startup script or php.ini configuration file. While it’s ok for most php application, AjaXplorer must know what character encoding the filename use in order to display them correctly.
A usual safe value is UTF-8, as most Posix system use UTF-8 internally because it’s language independant.
If you don’t know what to put there, you should try this:
AjaXplorer remote filesystems repositories tries to detect remote filesystem encoding, so you shouldn’t have to fix it for remote filesystems (ssh, ftp, remote access).
In some case, we have detected problems with the gzip encoding and some browsers. Since AjaXplorer 2.3.8, there is an option that allow you to disable gzip encoding. Depending on the version, it will be either in server/conf/conf.php (until 3.2.4), or directly editable via the GUI in the Settings, by editing AjaXplorer Core options (after).
In the first case, you should replace :
define(‘GZIP_DOWNLOAD’, true);
with
define(‘GZIP_DOWNLOAD’, false);
In the server/conf/conf.php file, there is a folder defined by PUBLIC_DOWNLOAD_FOLDER, that is by default pointing to YOUR_INSTALL_PATH/public. You have to create this folder and make it writeable by the server, to see the « Public URL » action appear in the GUI.
Of course, you can point to a different folder. By default, this will then generate a link with the current ajaxplorer URL followed by « /public/ » and the php file. But you can change this URL by editing the PUBLIC_DOWNLOAD_URL to whatever you want. That way, your ajaxplorer can be in a private zone, and create public links inside a public zone.
You can add the following instruction in your server/conf/base.conf.php file, just after the init_set(« session.cookie_httponly », 1) call :
session_set_cookie_params(0, dirname($_SERVER['REQUEST_URI']));
This will ensure that the session cookie only concerns a given URI of your domain, and thus cookies won’t be shared between the various instances.
Use the Default Rights parameter of a repository configuration. Allowed Values are « r » (read), « w » (write) and « rw » (read write). If you’re dealing with the default repository, this is done inside the server/conf/conf.php file, inside the DEFAULT_RIGHTS array key.
As admin, open the Settings window, click Create Repository and in the Path form, use the AJXP_USER keyword to create a path that will be adapted to each user. For example, use the following configuration:
Repository Label : My Files
Driver : File System
Path : AJXP_INSTALL_PATH/files/AJXP_USER
Create : Yes
Recycle bin folder : recycle_bin
(Each user will have their own unique repository and the admin can view them when browsing the Default Repository packed with AjaXplorer.)
[From version 4, the "Open with..." action allows you to choose any editor to open any extension type, and will remember this choice as a user preference]
Go to the plugin editor you are interested in, and open the file plugins/editor.editor_name/manifest.xml. Inside this file, you can see an attribute « mimes » of the main document element, « <editor> ». Just append the files extensions you want here, separated by commas.
If you are using a version superior to 3.3.X, add first a metastore.serial Meta Source to the repository.
Add a « Meta Source » to your repository (either via the GUI or the bootstrap_repositories.php file, depending on where your repository is defined), using the meta.serial plugin. As a « meta_field » use the specific keyword « stars_rate », and as « meta_label », whatever you want, « Rating » for example.
See more about meta.serial plugin here.
In AjaXplorer, all actions are defined and aggregated inside XML files. These files are brought to the application generally via plugins, except for some very basic actions defined in server/xml/*.xml. First thing is to see what plugins are active (basically, if you have no idea, search in access.fs, conf.serial and auth.serial), and look for the <action name= »the_action »></action> XML block. Comment the whole bloc (using <!– comment content –> markers) if you want to totally disable the action, or finetune the attributes of the action if you want to leave the action enable but just remove it from the toolbar, the contextual menu,etc.
Open the file plugins/gui.ajax/manifest.xml and modify the <property> inside the <component_config className= »FilesList »> tag. « thumbSize » accept only numeric values, « displayMode » accept only « list » or « thumb » values. Warning, both properties are overriden by user’s preferences, so you should test your changes on a clean user (create a new one for tests purposes).
Yes there is, check the notify.phpmail-lite plugin.
Yes, check AjaXplorer Plugins > Meta Plugins in the documentation, use the meta.serial plugin with the special keyword « css_label ».
DISPLAY : If you are using the standard filesystem driver, there is a specific configuration file that you can edit to limit some file extensions or folders to be displayed in AjaXplorer. Open the file server/conf/conf.access.fs.inc and edit the specific configuration variables (from version 4 and later, you can edit these values directly by editing the access.fs plugin options) :
UPLOAD : For the upload part, it’s not done via configuration, but you can easily hack one file to suit your needs. Open the file plugins/uploader.flex/flash_tpl.htmlat line 8 :
You can see :
>> $FlashVar = ‘&fileTypes=*.*&fileTypeDescription=All%20files&totalUploadSize=’.$confTotalSize.’ [.... end of line]
You can edit the « fileTypes » and « fileTypeDescription » variable using for instance the following syntax :
>> [...]&fileTypes=*.doc;*.jpg;*.gif&fileTypeDescription=My%20Type%20Description&[...]
Be aware of replacing the « space » by %20 in the description. Once you’ve made changes, clear your browser cache to be sure to see your changes happen.
As long as you do not modify AjaXplorer deeply (modifications like theming or little tweaks are not taken into account), and as long as you leave a link to the source code (i.e. to this website, except if you want to host the source code on your own website) on the user-interface (this is the particularity of AGPL against GPL), yes you can.
For example, if you change the logo of the splashscreen (using the gui.ajax plugin options) and let the « Powered by AjaXplorer » mention, this will be ok. If you want to remove this reference, you should contact us.
Under the very strict AGPL conditions as explained above (leaving the source code link), yes, you can. But beware that this means that you must publish every modification you make to the code, and as the license is « copyleft », you will probably also have to publish the rest of your administration panel under a compatible license if ajaxplorer is integrated with it. So you’d probably want to contact us and buy a specific commercial friendly license.
As long as your software license is compatible with the AGPL, and that the modifications are published, and that you leave the link on the user interface, YES.
If you software license is not open-source or not compatible with AGPL, NO, you can’t. But you can contact me and we can discuss an alternative licensing model that would allow you to do so.
The flash uploader is in fact not pure flash but FLEX, based on the FLEX3.0 library. You can download a free version of the compiler on Adobe website. The ActionScript and MXML sources can be found in the AjaXplorer SVN, below the trunk/core/flex. More info at http://sourceforge.net/scm/?type=svn&group_id=192639
As admin, open the Settings repository. You probably see a Logs tab but nothing listed inside of it. If so, there is probably a write permission missing — the « logs » folder is created inside the « server » folder. Thus the /path/to/install/server/ folder should be writeable.
Change the $AJXP_JS_DEBUG variable to true in the configuration file. After doing so, AjaXplorer will load all JS files and CSS files separately, instead of the big compressed file used normally.
The AjaXporer default GUI is defined inside the plugin gui.ajax. As you can see, the content of the « ajxp_desktop » (i.e. the application main zone) is described here precisely. Now have a look at the hook.demo plugin : you can see sample of HTML snippets added « before » and « after » the main « ajxp_desktop ». Best way is to activate the hook.demo properly and put your own header/footers here, so that it won’t be overriden by a future update. More easy can be to copy the hook.demo samples inside the gui.ajax.
Read the plugins section of this documentation, as well as the developper doc!
Powered by WP exec PHP.
