Be the first to post a text review of PLICITY CMS. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• plicitycms plicity-1.0.5 file released: plicity-1.0.5.zip

  V1.0.5 *************************************************************************************************** * Bugfixes / Changes: *************************************************************************************************** #NB-1050-1 * Removed $cp_db_charset, $cp_frontend_charset and $cp_backend_charset global variables from reference configuration cp-config-sample.php. * Added content_type_frontend and content_type_backend keys to options table (default value is text/html; charset=ISO-8859-1) * Replaced global $cp_backend_charset with value from option-key content_type_backend in default backend header (admin/ui-templates/cp-header.php). * Removed deprecated globals from classes/admin/cp-ui.php file. #NB-1050-2 Added correct header encoding (ISO-8859-1) to admin/ajax-servers/cp-as-manage-pages-cm.php. #NB-1050-3 Fixed a bug which made it possible to copy&paste / cut&paste pages into the root level of a PLICITY page tree. The operation is no longer possible as of PLICITY 1.0.5. #NB-1050-4 Improved performance of the cp_table_inspector::get_columns_from_table() function for large tables. #NB-1050-5 Changed cp_options.option_key to type VARCHAR(255) in order to improve option query performance. #NB-1050-6 Improved overall database performance by adding new MySQL indexes. #NB-1050-7 Removed trailing space behind ?> in admin/cp-admin-settings.php. #NB-1050-8 Fixed an issue with PLICITY installation. When the PLICITY database is not yet populated for new PLICITY installations, the cpdb class in classes/cp-db.php does now output a warning and suggests the user to proceed to the PLICITY installation script. *************************************************************************************************** * Additions *************************************************************************************************** No additions were made in this release.

  posted 378 days ago

• File released: /plicitycms/plicity-1.0.5/plicity-1.0.5.zip

  posted 378 days ago

• plicitycms plicity-1.0.4 file released: plicity-1.0.4.zip

  V1.0.4 *************************************************************************************************** * Bugfixes / Changes: *************************************************************************************************** #NB-1040-1 Fixed a bug in the extension backend module (cp-admin-extensions.php). The bundle and suite strings are now listed correctly in the extension table. #NB-1040-2 cp_content_list::retrieve() does now return the retrieved object as an array. #NB-1040-3 EditArea has been updated to 0.7.2.2. #NB-1040-4 Fixed a bug in page editor on creating a new page. The public time control is now set to the current time instead of displaying 1970-01-01 00:00:00. #NB-1040-5 Fixed translations (backend). *************************************************************************************************** * Additions ***************************************************************************************************

  posted 425 days ago

• File released: /plicitycms/plicity-1.0.4/plicity-1.0.4.zip

  posted 426 days ago

• plicitycms plicity-1.0.3 file released: plicity-1.0.3.zip

  V1.0.3 *************************************************************************************************** * Bugfixes / Changes: *************************************************************************************************** #NB-1030-1 Fixed misc. minor bugs in the PLICITY updating mechanism. Incremental updates are now run only if really required. In previous versions all update scripts were run regardless of whether this was required or not. This issue has been fixed with NB-1030-1. Made forced updates possible for debug / development purposes. Forced updates can be performed by calling admin/cp-admin-udpate.php?reason=forced_update&version=x.x.x.x (you must be logged in as admin). #NB-1030-2 Introduced database repair class (classes/admin/cp-repair-database.php). The class encapsulates a number of functions related to checking and repairing the PLICITY (core) database. #NB-1030-3 Introduced content-table field 'has_children' which acts as a performance flag for content objects. For that purpose a new function was added to the cp_content class named update_has_children_flag(). Calls to that function have been added respectively to the page editor (admin/cp-admin-edit-page.php). The cp_content::has_children() function has been optimized to use the flag in order to improve performance. The page management tree has been optimized to utilize the function in order to improve performance when working with the page tree in the backend. Navigational extensions can now make use of the cp_content_group and cp_content class to minimize the number of required SQL queries by utilizing the cp_content_group::get_content_objs() and cp_content::has_children() function. Note: The system does now call a new function, cp_content::notify_linkage_changed() whenever tree linkage is changed for a given content object. This does automatically update the has_children flag via a call to cp_content::update_has_children_flag(). #NB-1030-4 Changed order of controls in page editor sidebar. This relates to A-1030-3. #NB-1030-5 Removed function cp_get_datetime_modify_control() and cp_get_date_modify_control() from file include/cp-functions-datetime.php. The functions become obsolete and must no longer be used. #NB-1030-6 Changed cp_search_result::cp_search_result() to use the shorten_text() function for generating the content_excerpt member variable's content. #NB-1030-7 Fixed a bug in function cp_content::update_search_cache_entry(). The function does from now on only include text fragments within the search cache. In prior versions all content of all fragments were included in the search cache resulting in ID numbers presented to the user in search results sometimes. This is a temporary solution to this issue. In future versions a flag will be added to the fragment types table. This flag will determine whether a specific fragment type supports indexing for the search cache. This feature is likely to be added in release 1.0.4. #NB-1030-8 Added exit(0) statements behind all standard header("Location: ...") calls. #NB-1030-9 Removed trailing spaces beind <?php ... ?> in: * cp-content-group.php * cp-content-image.php * cp-error-manager.php * cp-functions-cache.php * cp-functions-content.php * cp-functions-l10n.php * cp-functions-server.php * cp-admin-functions-medialib.php * cp-admin-functions-updating.php * cp-functions-content-negotiation.php.php * cp-functions-content-structure.php * cp-functions-html.php * cp-functions-mysql-helper.php * cp-functions-word-count.php * gettext.php * JSON.php * Test-JSON.php * cp-extension-api.php * Browscap.php * cp-db-l10n-admin.php * cp-language-manager.php * cp-page-editor-state.php * cp-insertable-fragment-type.php * cp-insertable-fragment-type-manager.php * cp-table-inspector.php * bad_aliases.php * builtin_fragment_type_data.php This fix improves stability on servers with PHP configurations that do non-buffered output in combination with header-based redirects. *************************************************************************************************** * Additions *************************************************************************************************** #A-1030-1 Added two new global variables in global array $cp_globals. - (a) $cp_globals["override_homepath"] = "..."; // overrides the PLICITY homepath set in database - (b) $cp_globals["override_cms_path"] = "..."; // overrides the PLICITY cms_path set in database The cp_options class (classes/cp-options.php) was modified / extended in order to implement the functionality of overriding cms / homepaths. #A-1030-2 Added / updated various source code documentation. #A-1030-3 Added public time control for pages in page editor. Added function cp_make_mysql_datetime() to file include/cp-functions-datetime.php.

  posted 447 days ago

• File released: /plicitycms/plicity-1.0.3/plicity-1.0.3.zip

  posted 447 days ago

• plicitycms plicitycms-1.0.2 file released: plicity-1.0.2.zip

  V1.0.2 *************************************************************************************************** * Bugfixes / Changes: *************************************************************************************************** #NB-1020-1 Fixed a bug in cp_content_group::create() function (in classes/cp-content-group.php). Under certain conditions wrong indices for new group list entries were determined in prior versions. This issue has been resolved with NB-1020-1. #NB-1020-2 Fixed a bug in cp_content_list::retrieve() function (classes/cp-content-list.php). In prior versions the function did not retrieve the first meta value set for a page enumerated in the retrieved listings. *************************************************************************************************** * Additions *************************************************************************************************** No additions have been made in this release.

  posted 465 days ago

• File released: /plicitycms/plicitycms-1.0.2/plicity-1.0.2.zip

  posted 465 days ago

• plicitycms plicity-1.0.1 file released: plicity-1.0.1.zip

  V1.0.1 *************************************************************************************************** * Bugfixes / Changes: *************************************************************************************************** #NB-1010-1 Changes in cp_content_group class: * Extended cp_content_group::get_content_objs() function to include named tables in queries and thus allow for sub-SELECTs in $order_by parameter. * Changed function cp_content_group::get_content_objs() to work in collaboration with the cp_content_list class in order to reduce the number of queries required to fetch a group of content objects. This is a performance improvement only. #NB-1010-2 Corrected and extended the PLICITY about dialog. #NB-1010-3 Fixed a bug in the cp_content::create() function. The $title_nav parameter is now inserted into the respective database field on page creation appropriately. #NB-1010-4 Fixed a bug in path defines in cp_settings.php (PATH_CONTENT_MEDIA_TEMP), which prevented users from uploading user pictures via the admin interface. #NB-1010-5 Added $debug_queries member variable to the cpdb class. Setting $cpdb->debug_queries to true will cause the cpdb::query() function to output queries on the standard output. The default value for this member variable is false. #NB-1010-6 Corrected the bail message's layout in cpdb::bail(). #NB-1010-7 Fixed a bug with the displayment of a new system version in cp-admin-update.php on automatic database updating. #NB-1010-8 Fixed various (german) translations. #NB-1010-9 Fixed cp_extension_manager::restore_extension_tables() to work with special chars in table column names. #NB-1010-10 Fixed loading of frontend gnuGetText locale (in cp-settings.php). The code for calling the cp_gettext_load_default_textdomains() function was moved behind the $cpdb_l10n initialization section, so that the correct current locale is set when the gettext frontend locale is loaded. Prior versions of PLICITY did not load the default frontend locale in all cases, which led to no translation of the default frontend gettext strings. #NB-1010-11 Changed cp_header::render(). Added a new parameter called $to_buffer. The parameter is filled by the cp_content::render() function, which was changed accordingly. In fact, $to_buffer is passed through from the cp_content::render() function to the cp_header::render() function. This parameter was added in order to enable header templates to incorporate the value of $to_buffer into their programmatic behavior. #NB-1010-12 Fixed a bug in the cp_content::get_children() function. The function does now deliver an array of cp_content objects as described. The previous (wrong) behavior of the function was to return database objects instead of cp_content class instances. #NB-1010-13 Fixed a bug in the cp_content::update_vpath_entry() function. The function did not update the vpath entries of child pages. This led to a problem when renaming the alias of a parent page and then linking to one of its child pages with the new (actually correct) vpath. #NB-1010-14 Fixed a bug in file cp-admin-edit-page-group.php. Renaming group keys was performed in the wrong localization interface causing the system to rename a group key only for the current backend locale and therefore opening the door for inconsistencies. In order to resolve this bug the cp_db_object class was extended. Modifications to the cp_db_object class: Functions update_var() and update_var_multilanguage() received a new parameter at the end of their paramters lists, which is called $interface and defaults to 'frontend' in both cases. That is existing code does not have to be changed and will continue to work as expected. The function is now also fully applicable to the backend interface by specifying 'backend' for the $interface parameter. *************************************************************************************************** * Additions *************************************************************************************************** #A-1010-1 Added various comments for the PLICITY reference documentation.

  posted 476 days ago

• File released: /plicitycms/plicity-1.0.1/plicity-1.0.1.zip

  posted 476 days ago