Pligg Support

How to change Upcoming as new in my old database..

Possible Answers

    Are you forget to upgrade new language file.

    Re-upload to the languages/lang_english.conf file.

    | Posted 928 days ago | Permalink | Hide Replies

    The upgrade script takes care of that for you.

    | Posted 928 days ago | Permalink | Hide Replies

    Follow the normal routine for upgrading between Pligg versions. For the most up to date directions, view the readme.html file included with Pligg CMS. Below is a shortened version:

    1. Backup your files and database. Double check it to make sure that it's a valid backup.

    2. (Optional) Place a file named ".maintenance" (without the quotes, but with the period at the beginning) in the root directory of your Pligg website. This will enable a "Maintenance" mode when Pligg 2.0.0 files are added in the next step. This step is excluded from the official upgrade

    3. Upload the new Pligg 2.0.0 files to your server, overwriting your Pligg 1.0.0 files.

    4. Visit /install/upgrade.php and follow the steps on the page to upgrade your database to Pligg 2.0.0.

    5. Remove all of the files from the /cache directory, except .htaccess and index.html

    6. (Optional) If you followed step 2, remove the .maintenance file from your server to disable maintenance mode.

    I believe that the 2.0.0 upgrade may change your template settings for you to "bootstrap". If this is not the case, then you should set the template value to "bootstrap" on the Template Settings page: /admin/admin_config.php?page=Template.


    Now considering your more specific question, the Pligg upgrade script should automatically convert 'upcoming' statuses in the database to 'new'. If this is not the case, file a bug report on GitHub:

    | Posted 928 days ago | Permalink | Hide Replies
    | Posted 928 days ago | Permalink | Hide Replies | Show / Hide

    I can see the page when I call the new.php file rather than the URL friendly /new/. This tells me that you forgot to copy over the new version of the .htaccess file. Open htaccess.default and copy it into the server's .htaccess file. This file doesn't get upgraded automatically (which is one reason why it comes as a .default file), because it contains user-configurable values that some people need to set.

    | Posted 928 days ago | Permalink | Hide Replies

Who Upvoted this Story's Support area is where you can ask questions and get answers. Just getting started with the Support area? This section describes tips for participating.

Submitting a Question or Comment

By taking a minute to research previous posts you may receive an answer much faster than waiting for a response to a new question. Begin by searching the support section for an answer. Sometimes you may even want to extend your search to the entire domain.

If you are unable to find a relevant answer, submit a new question or comment here. Please provide a detailed description and, when necessary, debugging information such as your server environment (a link to a <?php phypinfo(); ?> .php page would be very helpful), your web browser, and any steps necessary to reproduce your issue.

Submitting an Answer

If you have an answer or useful response that you would like to add to a post, you can submit it as a comment which other users will then vote on. Answers are sorted by most popular to least, allowing the best information to climb to the top of the page.

Please read and vote for existing answers before submitting your own, as there may already be an acceptable answer provided. You can use the "Reply" link found within an answer to submit a response to it, in case you want to expand or comment on someone else's contribution.

Including Files or Code

Sometimes it is necessary for you to attach a file or include a snippet of code for others to reference in your response. In most cases, you can .zip up files and attach them to a question or answer using Pligg's file manager. At times though this may fail, and in these circumstances we recommend using a third party host. Below we are including a list of recommended websites where you can share easily share file uploads (or snippets of code) through the web.