Work progress for the new version release of Plikli CMS

A new Plikli CMS version will be released on August 31, 2019.

I would like to share with you the work done as of today. and in a few days I will post a list of the planned additional work until the release!

In addition, a Marketplace will be added to the forum to allow users and developers to showcase their templates, modules and widgets, free or paid AND DESIGNED SPECIFICALLY FOR PLIKLI CMS!

Enhancement

  • Plikli CMS is now fully compliant with PHP 7
  • Substituted the deprecated each() function with current() and foreach()
  • Gradually applying the PHP PSR-1 PSR-2: Coding Style Guide.
  • Enhanced the login attempts code.
  • Synchronized all language files by removing all obsolete definitions and adding the new ones where missing. Removed the Turkmen language file, composer.json and composer.lock
    NOTE THAT DUE TO TIME AND THE FUNNY GOOGLE TRANSLATION, ALL LANGUAGE FILES, OTHER THAN ENGLISH NEED TO BE EXAMINED BY ADMINS USING OTHER THAN THE DEFAULT ENGLISH LANGUAGE!
  • Modified code to accurately get the MySQL Server and Client API versions.
  • Added more statistical data and information to the Statistics Widget.
  • Implemented a better function to accurately close HTML tags when the story content is truncated and replaced with Read More.
  • Fixed the tags insert process. When inserting tags, the tags cache table was truncated and rebuilt after every submit and after every article editing, even if the tags where not edited. It was too much strain on the server and takes a long time when importing feeds with a lot of articles.
  • Introduced a new setting / feature, SMTP to test the email sending on localhost, even with a fake email address and removed the usage of phpmailer4 and phpmailer5. Every email sending feature is using the full phpmailer library. In addition, the message will be printed on the page after it is sent. Note that this feature is for development on localhost only and only Admins can test it.
  • Introduced new setting “Use the new Story layout?” and added new Dashboard setting to allow Admins to choose the Story layout they want in Dashboard -> Template Settings. Note that a minor cosmetic was applied to the default bootstrap template to give a different look to toolbar and content section of the story.
  • Converted all tables and columns TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci
  • Added a PRIMARY KEY to the total_story_views module.
  • populating the input text box with the accurate protocol (http / https) – Upload Module
  • added a caution explanation to the killspam feature
  • updated descriptions of allow draft, allow scheduled and Complete submission on Submit Step 2 to warn Admins that if Complete submission on Submit Step 2 is set to false, it will prevent allow draft and allow schedule features from working.

Bugs

  • Upon submitting and editing stories, tags fields are stripped from any character that is not alphanumeric, underscore, hyphen and comma. However, I noticed that RSS import tags with an apostrophe which is causing an error in the query. I applied more filtering to remove the apostrophe because it is also removed in the search.
  • Fixed a minor issue that is not causing any problem, caught by John on the Plikli forum. title are not trimmed and a space at the end of the title was replaced by a hyphen.
  • Fixed the special characters appearing in the description. Reference https://www.plikli.com/forum-2/general-support/all-rss-feeds-rssfeeds-php/
  • Fixed the “ALL” tags that appears in the tools bar under the story title. Reference https://www.plikli.com/forum-2/general-support/sitemap-links-per-page-and-all-tags/
  • Fixed the approved IP entries in /logs/approvedips.log. The IP was written with a space at the end, and therefore the check for the IP in the approved IPs log was always returning false.
  • Fixed the code where notify author is checked when an article is edited. There were no code to process the multiple categories when this setting is set to true in Dashboard -> Settings -> Submit -> Allow multiple categories, therefore the code checking the equality of the categories, if modified is always returning false and included in the notification email, even though the categories were not modified!
  • Fixed the error types that was only displaying the last error. Now uploading avatar errors is an array and displays all relevant errors. Files affected: profile.php and user_navigation.tpl
  • fixed 2 bugs to accurately pull the language definition from both subscribe to comments module and Plikli language files.
  • Fixed the sidebar_saved module to eliminate some errors in loading Plikli language file, and added Chinese language file.
  • fixed some php warnings and notices. (This work is ongoing)

Installation / upgrade

  • added protocol detection to warn to install SSL Certificate before installing Plikli CMS
  • Updated all install/upgrade files for the new version.
Share me!

8 thoughts on “Work progress for the new version release of Plikli CMS

  1. For unforeseen personal emergency, I am forced to delay the release of the new version of Plikli CMS between a week or 10 days maximum, as of August 31, 2019. So the release date will be at the latest on September 10, 2019.

  2. Latest news:
    Firstly, I apologize for the delay, but ironing the wrinkles resulting from bringing Plikli CMS to be compliant with PHP 7 is still in progress and taking more time than what the first tests revealed. In addition, not meeting a deadline, especially in major revamping an application happens to all the big top notch tech companies, so for this person (not a user) who started posting comments since yesterday, September 10th asking about the release, I would tell him to calm down and a set date can always be modified

    When some designated users tested it, in general, we fixed the errors, warning and notices that surfaced due to the difference between PHP versions 7 and 5 and to its own tolerance and methods, not to mention the difference between the MySQL versions used with each.

    Additional in depth testing revealed that quite a few features did work as they intended. Therefore, we dove into a lot of debugging and fixing codes to fix the broken features.

    I will not set a date for the release, but all I can promise is that it will be any day from now to the end of September 2019. I would rather being late than releasing a broken CMS.

  3. It is September 30, 2019 and as promised, I will post the new release BY MIDNIGHT MY TIMEZONE.
    First I want to address Daniel (kadush) by telling him that the joke is you and you got yourself a nice kick out of Plikli community!

    I guess most of the users know me by now, from Pligg to Kliqqi to Plikli forums. I am for the quality over quantity and I will never release a new version before testing it thoroughly, this means no beta that might be full of bugs and breaks just because some users are impatient!!!
    As I said earlier, a lot of bugs that caused major features to break in PHP 7. PHP 7 is not tolerant as PHP 5, therefore quite a few function calls demanded to be modified accordingly. In addition, MySQL 5.7+ also is different from older versions and columns types had to be altered to accommodate the standards of version 5.7.
    Result:
    – Installation of Plikli CMS version 4.1.5 is working like a charm
    Upgrade:
    I tested the upgrade on localhost and live servers, using different instances of Plikli 4.1.0 and different database sizes.
    Due to dropping old indexes and adding new ones, namely in the links table, which is normally very large, the upgrade script was timing out from the MySQL server.
    The best solution was to detect the size of each table and run an automatic upgrade via the upgrade script on all the tables that are less than 50 MB in size. The script will give you the all the MySQL statements that you must manually run in phpmyadmin for the tables that are larger than 50 MB.
    In my case, I was running the upgrade on a 300 MB and a 600 MB databases, out of which the links table was 250 MB in the first one and 569 MB in the second. All i got is to manually run 3 statements in phpmyadmin to upgrade the links table. Mind you that in phpmyadmin, the 3 statements took 8 minutes a 4 seconds. Now you know why the script was timing out.

Leave a Reply

Your email address will not be published. Required fields are marked *

Human Verification: In order to verify that you are a human and not a spam bot, please enter the answer into the following box below based on the instructions contained in the graphic.