[springhigh]

For anyone having a similar experience.

We had a problem with clearing browser cache in a corporate environment after the upgrade. The PM site was being cached on the corporate firewall , so nothing we did worked ( clearing PM server or browser cache ), users saw a spinning wheel they tried to move between steps.

Our solution was to change the default Apache site from domain-name.com to www.domain-name.com
And change any Trigger references in the DB

This forced the site to reload correctly.

This is what we changed to get apache to work

Code: Select all

Virtual Host port 443 

  <IfModule mod_rewrite.c>
        RewriteEngine On
        RewriteCond %{HTTPS} off
        # First rewrite to HTTPS:
        # Don't put www. here. If it is already there it will be included, if not
        # the subsequent rule will catch it.
        RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [^] [L,R=301]
        # Now, rewrite any request to the wrong domain to use www.
        # [NC] is a case-insensitive match
        RewriteCond %{HTTP_HOST} !^www\. [NC]
        RewriteRule .* https://www.%{HTTP_HOST}%{REQUEST_URI} [^] [L,R=301]
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteRule ^.*/(.*)$ app.php [QSA,L,NC]
      </IfModule>

Code: Select all

Virtual Host port 80

RewriteEngine On
RewriteCond %{HTTPS} off
# First rewrite to HTTPS:
# Don't put www. here. If it is already there it will be included, if not
# the subsequent rule will catch it.
RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [^] [L,R=301]
# Now, rewrite any request to the wrong domain to use www.
# [NC] is a case-insensitive match
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule .* https://www.%{HTTP_HOST}%{REQUEST_URI} [^] [L,R=301]

[amosbatto]

That's strange. I haven't heard of anyone else with this problem upgrading to PM 3.2.2.
Did you upgrade from 3.2 to 3.2.1 without any problem or was this the first time you upgraded?

[springhigh]

Hi Amos
It was been upgraded in stages from v3.0 EE.
It still has few small bugs her and there , but it works.
The only other thing changed was we moved to a new server to accommodate the required stack for 3.2.2 , but that all seems ok