upgrade 9.6.2 to 1.0.4, blank frontend, perfect backend!

Sorry for slow reply, in Australia, had to sleep!

I checked on webandflows suggestions;
I did a full backup of the site so I am able to check config, it is in the right place. (manager/includes)

Did you try clearing the cache? Yes, tried many times.
Also can you confirm the index.php file is complete (upload new copy?)
I just downloaded a new copy and installed,, no change.

Also can you confirm the correct path is: /var/www/html_pudding/index.php
Absolutly correct

I have care read the install notes, I don’t have an altered site and mostly just use a plain vanilla site.

Thanks for any other suggestions!

Paul

Can you try a fresh 1.0.4 install to see if the issue may be server related or upgrade related?

Hi,
still working on this

I have just installed a new Modx site and it works fine. you can see this (athough there’s little point, as it works) http://charities.alond.com.au/

As I’ve done little modifications to the original site, is is feasible to transfer the database across, or something similar?

Thanks Paul

EDIT: I should add, it must be something I’m doing wrong, as nobody else seems to be having any problems!

I would suspect that you’ve got some old snippet or plugin code that is conflicting with the newer version. Check your Elements (snippets and plugins especially); it could be a problem with an old copy of Wayfinder or Ditto hanging around. Does this happen both when you are logged in to the manager and when you aren’t? It could be a problem with the new QuickManager conflicting with the old QuickEdit plugin. Temporarily disable all plugins and see how it behaves.

Also go into your templates and temporarily remove snippets; the "bare" template should work fine, then you can add your snippets back until you find the one causing the problem. It may be something like a Ditto, search or Wayfinder snippet with parameters that are no longer valid for the newer version.

Thanks to all who helped.

After running through and disabling bits, I decided it was easier to downgrade.
I have reluctantly moved back to the old (backed up) site, and all is well.
To anybody reading this, there appears to be no real changes in the Dbase, and my site appears to be working OK.

Thanks again,

Paul

Sorry to hear you were unable to get things working with 1.0.4. If you ever want to try again on another server let me know.

Thanks AMDBuilder,
It’s not the server, as I can easily complete a working clean install, it must be something in the upgrade from 9.6.2 directly to 1.0.4 that doesn’t work correctly.
When I have some time I’ll try swapping dB’s into a clean 1.0.4 and see if that works.

Regards,

Paul

P.S. it’s quite funny, I run a Magento site and Magento has a reputation for being a nightmare to upgrade, and I’ve had more sucess with upgrades with that over the years! alond.com.au very odd
Thanks! Paul

It will work fine if you don’t upgrade (that includes uploading the new files as well as clearing the checkboxes in the installer) your snippets and plugins, although plugins are probably OK. But snippets do change, and especially if you upload the new assets/snippets/snippetname files then don’t upgrade the snippet in the installer it will cause problems. And upgrading old snippets entirely will often cause problems when the parameters have changed, although most do allow for some degree of backwards compaitiblity.

The blank front-end indicates a PHP error, and that will be in a snippet or plugin. The best way to test for this is to disable all plugins and remove all snippet tags from the template and the resource (including any snippets in TVs or chunks), then the page should work. Add back the plugins one by one, then the snippets, until you find the one that’s causing the problem.