[as13969]

Dear PM Support,

As suggested, we upgraded from 2.5.2 to 3.2.1 but after the upgrade we have encountered a few major issues .

1. Process and Tasks titles are not displaying
2. Reassign - Users and Process drop-down do not populate
3. Advanced Search - Users and Process drop-down do not populate

Could you please advise or point us what needs to be check to resolved this issues?

Below are the system info of PM 2.5.2 and PM 3.2.1 environment.

ProcessMaker Ver. 3.2.1 - community
Database : MySql (Version 5.6.43)
Web Server : Apache/2.4.39 OpenSSL/1.0.2r
PHP Version : 5.6.40

ProcessMaker Ver. 2.5.2 - community
Database : MySql (Version 5.6.16)
Web Server : Apache/2.4.7 OpenSSL/1.0.1h
PHP Version : 5.5.9

Thank you in advance.

Alfred

[scivray]

Hi,
Did you try this : https://wiki.processmaker.com/3.0/Clear ... List_Cache

HTH

[as13969]

Hi,
Did you try this : https://wiki.processmaker.com/3.0/Clear ... List_Cache

HTH

Hi,

Thanks for the reply. We did clear the cache in PM setting but still not displaying the process and task titles and user dropdown do not populate user names.

[scivray]

You can check if your table APP_CACHE_VIEW is empty or not. The cache clear should truncate this table and recreate rows (by the way if you changed locale after installation, you have to manually update the triggers as explained in documentation).

[amosbatto]

To rebuild the APP_CACHE_VIEW table, see https://wiki.processmaker.com/3.0/Clear ... List_Cache

[as13969]

Hi amosbatto and scivray,

Thank you for your replies.

We performed the case list cache builder and the APP_CACHE_VIEW is not empty. Attached are the screenshots of build list cache and language setting of 2.5 and 3.2.1 PM version. We just noticed that during the upgrade other languages are installed. We only used 'English' in version 2.5.

[amosbatto]

Did you follow the steps listed here?
https://wiki.processmaker.com/3.2/Proce ... ocedure%0A

[as13969]

Hi amosbatto,

This is what we did, we followed this documentation https://wiki.processmaker.com/3.3/Proce ... grade_Plan

Two things are different :
- We upgraded 2.5.2 to 3.2.1 instead of the 3.2.2 or 3.2.3 recommendation in the article
- We have not upgraded 3.2.1 to 3.3 yet so the current environment is 3.2.1

Process simplified :
- Create Windows Server 2016 VPS
- Install php 5.6, MySQL 5.6, Apache 2.4 stack
- Migrated \Opt file structure to new VPS
- Migrated all PM databases and PM database users to new VPS MySQL
- Ran the update values in CONTENT table SQL for both workspaces
- Extracted 3.2.1 tarball in \Opt\processmaker
- Ran the php -f processmaker upgrade command, errors were encountered (see attached text file)

Awaiting for your reply.

Thanks, in advance.

Alfred

[amosbatto]

Alfred, Hopefully you have a backup of your PM 2.5.2 installation, because you are going to need to restore it.
Then, you need to follow this procedure to upgrade from version 2.5.2 to 3.0.1.8:
https://wiki.processmaker.com/3.0/Upgra ... ocessMaker

Then follow these instructions to upgrade from 3.0.1.8 to 3.2.1:
https://wiki.processmaker.com/3.2/Upgra ... ocessMaker
https://wiki.processmaker.com/3.2/Proce ... grade_Plan

If you are using the Community Edition, I do not recommend upgrading beyond 3.2.1 at this time due to these bugs:
https://www.pmusers.com/index.php/Bugs_ ... _upgrading

If you want to transfer to a different server, first upgrade to 3.2.1 on your existing server and backup your workspace. Then, install version 3.2.1 on your new server and import the workspace into your new installation of ProcessMaker.

PS: ProcessMaker Inc. can do the upgrade for you if you have a support contract.