Getting computer message downloaded new change log version 0.6

B Fix bug when adding new items to sorting field. A Integrated CoalaWeb Zones into version field. A Integrated CoalaWeb Gears into version field. A Integrated CoalaWeb Markdown into version field. A Integrated CoalaWeb Versions into version field.

A Integrated CoalaWeb Github into version field. General Compatible with PHP 5. Bug fixes for 1. Fixed a bug in the language class when outputting an error for an unfound file.

Fixed a bug to prevent PHP errors when attempting to use sendmail on servers that have manually disabled the PHP popen function. Added more accurate error reporting for the Email library when using sendmail. Removed a strict type check from the rotate function of the Image Manipulation Class.

Added enhanced error checking in file saving in the Image library when using the GD lib. Added a doctype function to the HTML helper. Fixed a bug where adding a primary key through Forge could fail Fixed a bug when using DB cache on multiple databases Fixed a bug in which identifers were not being escaped properly when reserved characters were used.

Fixed a bug with the regular expression used to protect submitted paragraph tags in auto typography. Fixed a bug where double dashes within tag attributes were being converted to em dash entities. Fixed a bug where double spaces within tag attributes were being converted to non-breaking space entities. Fixed a bug with high ascii characters in subject and from email headers. Fixed a bug when an opening quote is preceded by a paragraph tag and immediately followed by another tag.

Fixed a bug in the Text Helper character limiter where the provided limit intersects the last word of the string. It simplifies setting rules and field names, supports arrays as field names, allows groups of validation rules to be saved in a config file, and adds some helper functions for use in view files. Please note that the old Validation class is now deprecated. We will leave it in the library folder for some time so that existing applications that use it will not break, but you are encouraged to migrate to the new version.

Updated the Sessions class so that any custom data being saved gets stored to a database rather than the session cookie assuming you are using a database to store session data , permitting much more data to be saved. Please see the Loader class for more info. Improved Parser class to allow multiple calls to the parse function. The output of each is appended in the output. Database Improved Active Record class to allow full path column and table names: hostname.

Also improved the alias handling. Improved how table and column names are escaped and prefixed. It now honors full path names when adding prefixes and escaping. Added driver name variable in each DB driver, based on bug report These are intended to be used on their own, or with the new Form Validation Class.

Added meta function to HTML helper. Improved accuracy of calculations in Number helper. Added a few openxml document mime types, and an additional mobile agent to mimes. Added a file lock check during caching, before trying to write to the file. Modified Cookie key cleaning to unset a few troublesome key names that can be present in certain environments, preventing CI from halting execution.

Fixed assorted user guide typos or examples , , , , , , , , , , , , Fixed an edit from 1. Fixed a bug in the Email library with quoted-printable encoding improperly encoding space and tab characters. Fixed a bug in the Session class when database sessions are used where upon session update all userdata would be errantly written to the session cookie.

Fixed a bug in backups with the MySQL driver where some legacy code was causing certain characters to be double escaped. Fixed a routing bug that occurred when the default route pointed to a subfolder. Fixed a bug that was ignoring case when comparing controller methods Fixed a bug that was not setting SMTP authorization settings when using the initialize function. Fixed Oracle bug that was preventing multiple queries in one action. Fixed ODBC bug that was ignoring connection params due to its use of a constructor.

Added brackets around database name in MS SQL driver when selecting the database, in the event that reserved characters are used in the name. A path was not defined for NetPBM. Fixed DB backup bug in which field names were not being escaped. Fixed a DB Active Record caching bug in which multiple calls to cached data were not being honored.

Fixed a bug in the Session class that was disallowing slashes in the serialized array. Fixed a spelling error in a Loader error message. Fixed a bug with IP validation with empty segments. Fixed a bug in which the parser was being greedy if multiple identical sets of tags were encountered. Libraries Set the mime type check in the Upload class to reference the global mimes variable.

Added support for query strings to the Pagination class , automatically detected or explicitly declared. Documented get in the Input class. Added the ability to automatically output language items as form labels in the Language class. Helpers Added a Language helper. Added a Number helper.

Charset information in the userguide has been moved above title for internationalization purposes Amended fixes for bug with parsing DSN database connections. Fixed a bug with a regular expression in the Image library.

Removed some unused variables from the code Fixed assorted user guide typos or examples , Added quoted-printable headers to Email class when the multi-part override is used.

DB Forge is now assigned to any models that exist after loading Database Added Strict Mode to database transactions.

Added new user-modifiable file constants. Libraries Added increased security for filename handling in the Upload library. Added increased security for sessions for client-side data tampering. Unit Testing results are now colour coded, and a change was made to the default template of results.

The Zip class now exits within download. The Zip class has undergone a substantial re-write for speed and clarity thanks stanleyxu for the hard work and code contribution in bug report ! Changed the radio and checkbox functions to default to not checked by default. Scripts were deprecated in Version 1. If you still need to use them for legacy reasons, they must now be manually loaded in each Controller.

Added a Reserved Names page to the userguide, and migrated reserved controller names into it. Added a Common Functions page to the userguide for globally available functions.

Bugfixes for 1. Fixed a bug in DB Forge, when inserting an id field Fixed a bug in the table library that could cause identically constructed rows to be dropped Fixed a bug in AR compiling, where select statements with arguments got incorrectly escaped Fixed a bug in the Directory Helper where the directory resource was not being closed, and minor improvements. Fixed a bug in the Upload library that might output the same error twice Fixed an AR bug when joining with a table alias and table prefix Fixed a bug in the Table library where the integer 0 in cell data would be displayed as a blank cell.

Fixed a bug where SMTP emails were not having dot transformation performed on lines that begin with a dot. Fixed a bug where a URI containing slashes only e. Made Active Record fully database-prefix aware. Added a Path Helper. Modified method calling to controllers to show a when a private or protected method is accessed via a URL. Modified framework initiated s to log the controller and method for invalid requests. Use of numeric and integer are preferred. Made Active Record fully database prefix aware Fixed a bug in query binding Fixed a bug connecting to a database via a DSN string.

Fixed a bug where the routed segment array was not re-indexed to begin with 1 when the default controller is used. Fixed assorted user guide typos. All AR queries are backticked if appropriate to the database. Added support for limit into update and delete statements in Active Record. Added the ability to pass an array of tables to the delete statement in Active Record.

Added the ability to use aliases with joins in Active Record. Added a third parameter to set in Active Record that withholds escaping data. Previously they were always saved. If set to TRUE it will limit the result to only table names with the current prefix. Core changes Added ability to load multiple views, whose content will be appended to the output in the order loaded. Added the ability to auto-load Models. This can be helpfull when building affiliate websites.

Fix a Joomla 3. The symptom was that a message "You are not permitted to use that link to directly access that page xxx. Now when this happen during the update of a slave site, this error code is considered as success when the table already exists. Add the possibility to specify a language code associated to a domain name with the objective to allow the Multisites Menu Item, Article Sharing or other extensions using a specific domain name instead of the first one of the list according to the current language code.

Fix the Fix relatif to JRegistry implemented in J1. All Editions - Update the maintenance menu to add joomla 3. Bundled with Patches definition 1. A PHP Fatal error was raised when re-installing an extension for the slave site. The error was due to a regression bug in core J3. The present work arround add consists in adding the missing JRegistry declaration under J3. In the JMS Template, add the possibility to edit the action on the "index. Also improve the compatiblity with Joomla 3.

Fix the manifest files name to ensure that it is always in lowercase without spaces. Jms multisites for joomla version 1. Mainly add the compatibilty with Joomla 3. Prior version of JMS may crash the Joomla 3. In addition, the new Joomla 3. Therefore, it is strongly advised to install JMS 1. Ensure in the "maintenance" menu that each SQL statement ends with a ";" to make them valid when copied concatanated into the "Free SQL" field.

The Jms multisites version 1. The Jms multisite for joomla 1. JVital plugin used by agora-pro to avoid duplicated class definition that leads to a PHP Fatal error. In the previous version, only the verification that the table exists was performed without structure verification. The new default behavior is equivalent to "fix table". Fix bug in Joomla 3. Otherwise they might be unavailable when directories contain the word "view". It fixes the joomla 3.

Fix the re-installation of a module or a plugin from the slave site. The first time that JMS is installed, add the update of all the JMS Templates rule folder and files to take in account the currentmaster website directory. This avoid that the replicMasterXXXX or shareMasterXXXX rule miss some directories when the rules are not reviewed by the user and updated to take in account the current master directory structure.

This Jms Multisite version 1. For more technical details concerning the change introduced in Joomla 2. The symptom is that when you install a package, joomla 2. This result by the language file that are not installed or updated and the specific installation script that is not executed.

This Jms Multi Sites version mainly add definition to have a "hikashop multisite" and "hikamarket multisite". Hikamarket provide a multi vendor system and with the benefit of Jms Multi Sites, it is now possible to create specific website for a specific vendor that the other website does not see. In the same time, the "super store" can see the products of all vendors and also have a single inventory. Hikashop allows create website with categories that are specific to a specific website. So that the other website will not see the categories.

As in case of the hikamarket and vendor, the "super store" can see all the categories. So that you can for example, in the super store, searh product in all the categories of all the websites and in a specific website, just see the products of your own category. In HikaMarket multi-vendor, a new field is added to specify the Site ID for which this vendor should be displayed.

A problem in the package of the version 1. This jms multisite for joomla version 1. The Jms Multisite 1. The error is araise during the computation of the "refresh icon". On prior JMS version, it is possible to avoid the error when settings the "disable the refresh icon" to yes. See the settings menu. Jms multisite version 1. Jms Multi Sites version 1. The new Jms multisite version 1. Bundled with Jms multisite patches definition 1. Jms multisite for joomla 1. It is also bundled with the jms multisite patches definition 1.

Jms Multisite for joomla version 1. Jms multisite for joomla version 1. Under Joomla 2. This new jms multisite version 1. Several keywords are added to allow creating random value composed of alphanumeric characters or only letter or start with a letter followed by a random string or using and auto increment values. This is an error introduce in the Jms 1.

This version add a rescue registration in case where our hosting provider interrupt the connection during the transfert and return a cookie instead of the data. When Jms Multi Sites detects this case, it retries with an alternate solution during the registration. This Jms Multisite version contain the compatibility with Joomla 2. This avoid a Fatal Error when displaying the Front-End website creation on a template that has lost its DB or slave site. Another issue were identified when a site has an invalid DB connection.

In this case, the refresh icon generated an error and the list were not displayed. So now this side effect is fixed. In previous case, the work arround were to disable the display of the refresh icon by a setting in the "multisites.

Under Joomla 1. This new feature present in Joomla 1. In this case, Joomla is not able to render the string correctly and return an empty string. This problem is arised with the French version that we now converted in UTF We also disabled the Joomla 1. We also enhanced the processing of the site ID so that joomla 1. We also fix "notice message" that may appear when editing an existing template written by an Jms multisites version 1. This Jms Multi Sites, fix a bug in the new installer compatible with joomla 1.

When installing the 1. This version fix the fatal error that occurs after the save of the slave site when computing the redirection URL. When a new Joomla 1. We improved the compatibility with Joomla 1. Sometime, Joomla 1. This contain the patches for Joomla 1. Fix a bug to verify the condition when the "refresh icon" must be displayed. The fix now provide a Joomla 1. When displaying the "refresh icon", all the website DB are compared with its "website templates" DBs. We added a cache on the DB queries to improve the performance during the comparison of the DBs tables.

Add a verification that a DB does not exists when creating a DB dynamically. This Jms Multi Site release add a partial compatibility with the newer Joomla 1.

Jms Multi-Site is no more compatible with joomla 1. This Jms Multi Site version is also bundled with Joomla 1. Also add conditional implementation to take in account the new incompatibility between Joomla 1. So now Joomla 1. With the new Joomla 1.

So now, most of the patches consists in adding files to the Joomla 1. Also bundled with Joomla 1. When a large number of slave site needs to be managed, the time to compare the number of tables that are present in the master with all the slave site DB may be high. So now, it is possible to disable the "refresh icon" to speed-up refresh of the list of slave site present in the manage site.

This Jms Multisites patches definition add a patch for the All Video download script. The patch computes the "document root" directory based on the deployed directory. The sitePath "document root" directory was not correct when using Symbolic Link. Add a patch for the All Video download script to compute the "document root" directory based on the deployed directory.

The sitePath "document root" directory is not correct when using Symbolic Link. This Jms Multisite version add the compatibility with Joomla 1. It fixes severa screen rendering to work with Joomla 1. This Jms Multisites patch definition add a patch for Mobile Joomla to allow speciifc configuration for each slave sites. When the SEF is enabled, Joomla does not cleanup all the parameters when they are already present in the menu item id definition. In this "Article Sharing for JMS" we have added a cleanup of the parameters when they are already present in the menu item id.

Also purge all the converted files to remove the older caches. Otherwise you will get a duplicate "routing" definition error message. Kunena 1. If you want to install Kunena 1. We added the Joomla 1. This fix ensure that the MultisitesContent routing cache file is always stored in the multisites content directory and in the directory from which the multisitescontent is called.

The new patch try to identify the signature of AceSEF 1. This new patch is required for AceSEF 1. To align the URL between the menu computed by Joomla and the URL present in the front-end website creation forms, we have computed all the form actions to provide the same SEF urls than the menu.

The new SEF url compute in the front-end were tested on Joomla 1. Here are the changes performed to increase the compatibility with Joomla 1. It is now possible install JMS Multisites on joomla 1. We still consider this JMS Multisites version as an alpha version for joomla 1.

The reason is that Joomla has changed plenty API that sometimes require that we implement specific things for joomla 1.

For the moment, it is possible :. Add a check when an alias link is already present on the disk with another value. In this case this report an error and the slave site is not created.

This Jms multisites version contain several update to provide a partial compatibility with Joomla 1. Between the Joomla 1. This version reduce the compatibility problem between Joomla 1. We know that the JMS tools and the layout are still not working and that the new Joomla 1.

In addition, the language files processing were totally rewritten by Joomla and now it is no more allowed to enter html tags into the language file. All these issues are not yet solved. This is the reason why we still consider this Jms Multisites version as a alpha version event if the JMS kernel is not modified and is identical between Joomla 1.

This Jms Multisites patch definition 1. When the patch is not correctly installed, it may happen that the access to the standard Joomla "manage template" is corrupted. Modify several patches to take in account the new Jms multisites "letter tree" directory structure. We have introduced a new way to save the Jms Multisites slave site description on the disk to allow record a lot of slave sites definition and reduce the impact on the OS performance.

Now, it is possible to store the Jms Multisites slave sites configuration using a set of directories using a tree of letters to speedup the files access. By default this new low level directory structure is not enabled and is a parameter present in the "multisites. This new way to save the multisites configuration file may be usefull when proposing a huge number of websites creation from the front-end.

This functionality is already live with a customer who expect more than 1 million slave sites and that use a multisites affiliate program that we have developed. To speedup the processing when the Top Level Domain definition is not required, we also add a parameter in the "multisites. When installing an update of Jms Multisites, we know detect if a "multisites. The "mutlisites.

New multisites. Call plugin function to give the opportunity to contributor write specific patches that could be appended to Jms Multisites. A free plugin for the YooThemes WARP framework is provide with the contribution of Brett Bruce that written the patches and that we encapsulated into this new plugin facility. Call plugin multisites to defined the patches. It also exists now the possibility to implement plugins to process additional customer specific keywords.

Modify several existing patches to take in account the new letter tree directory structure used when there are a lot of slave sites. This Jms multisites version is just bundled with the latest joomla 1.

It is recommended that you update Jms multisites to a version 1. Includes the fix concerning the bug introduced by Joomla in the version 1. The behavior is that Joomla 1. Some side effect were also noticed in live site. With Jms multisites, you can already benefit of this fix that had the sided effect to prevent any login.

Also add several cross-check on joomla patches installed to improve consistency when joomla restore or replace existing files that remove Jms multisites patches. A side effect detected is an infinite loop when installing the joomla patches from version 1. The infinite loop is due to the fact that the installation directory exists restored by JMS and when updating 1.

That include the fix concerning the bug introduced by Joomla in the version 1. We strongly recommend to install the Jms multisites patches 1. In Jms Multisites for joomla 1. In this version, we have removed the generation of the "secret" value to keep the same value than the master. Therefore the JReviews extension that expect to have different secret values to have specific configuration now share the configuration.

If you have created slave site with Jms Multisite 1. The objective is to use the same secret value for all the slave sites. When creating a slave site, it may happen that some existing view contain additional statement like "select To retreive the retreiving "FROM table name" present in a statement we add a cross-check that select the word that is preceded with the word "from".

In this case, you select the slave site or template definition that you want to use when creating the "new" definition. This maybe helpfull when creating a Jms templates where you have to setup the "folders and files" actions. You can re-use an existing definition that is moreless identical to the one that you want to create. Also add in the "manage site" a search filter that allow quickly find a specific slave site definition. This maybe usefull when you have several hundred of websites.

The search is applied on fields:. To reduce the packaging distribution we have removed from Jms multisite for joomla all the original files of joomla 1. So there is no more "rescue" algorithm available in Jms to restore original joomla files in case of "uninstall" or patches installation failure.

This does not mean that Jms will not work with older version of joomla. There is no more rescue or backup guarantee with older joomla versions. Joomla uses the "secret" field present in the "configuration. In case where you replicate an existing website, Jms multisite uses the existing "configuration. This patch consists in generating a new "secret" value with the objective to have specific "cache" files event when sharing the same cache directory.

This may be usefull for "Windows" platform that can not use the Symbolic Link and may not be able to have a specific "cache" directory. Some extension like "JReviews" also use the "secret" value to store their own configuration file on the disk. Patch definition 1. Add JMS Tools install definitions for :. JMS does not syncrhonize files on the disk. It just consists in copying the file mentionned by JMS in the "check for patches".

This definition present risks in terms of the consistency and should only be used by advanced user and at their own risks. When the partial sharing is used It is required that the AcyMailing plugins that import content except user details should be de-activated.

We strongly advise the users who would like to use the partial sharing that they test themselve the behavior before applying such configuration in production. The objective is to ignore the installation of the patch when using a "starter" AcyMailing that does not contain any license free version.

When a port is present in a URL received by JMS, the domain was "ignored" event when it was present in the list of domain. The fix consists in using the domain name when it is present as a slave. As the port is present in the URL the request was posted on the master website instead of the "www.

To install the fix, it is required to "uninstall" the JMS patches and "re-install" the new patches present in the JMS 1. It is possible to setup automatically the new FTP layer parameters that must be written into the slave site configuration. This allow to automate the procedure described in the tutorial video In JMS templates, it is now possible to ignore the creation of the the images and templates folder.

This is usefull when creating a JMS template that is deployed in the same directory than the master website case of Windows platform.

This allow creating rule where deploy folder is totally empty No Symbolic Links at all. For the website creation from the front-end, it is now possible to chose which fields must be entered by the customer. Revenant ». You deserve a cookie for this. Thank you so much. Sarissofoi Captain Posts: If only you could make similar for global speed.

Kulverstukass Ensign Posts: With a thank you, I'd like to point out that there is no effect if player is not present on battlefield. Can't say if it applies to retreat, though. Another advantage of this installation program is that it will see if the Access runtime is required and if it is, it will prompt you to download and install it. We no longer need to create distributions that include the runtime modules Work continues on the Version 0. This release will be the first of two focusing on the reporting capabilities of the database.

The primary update that you will notice in this release is the ability to create your own custom reports. This has taken the bulk of the development time for this particular release far more than I thought it would.

For this reason, we will release Version 0. Our hope is that the 0. Our goal is to have the 0. We will keep you updated on our progress.

We are pleased to report that we have released the latest update to the Flight Logs database program. This update includes a number of new features that include: - A Builder's Log that will help you record your progress during construction of your rockets.

Including time spent, costs, and adding attachments - A Maintenance Log that records any maintenance you do on your rockets.