Forums / Install & configuration / Urgent help required: can't add content after upgrade to 3.2

Urgent help required: can't add content after upgrade to 3.2

Author Message

Jason Filby

Thursday 09 October 2003 1:33:05 am

Hi all

I need urgent help here. After upgrading to 3.2 I can't add content to the site. After clicking on Publish the new content (adding or updating) just isn't there - and there's no error message either. Any ideas on how I can track the problem?

Thanks
Jason

Tony Wood

Thursday 09 October 2003 3:21:55 am

What were you upgrading from?
Have you checked in the database to see if content is there.
Try checking permissions too.. it always get me.

Tony

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Jason Filby

Thursday 09 October 2003 5:06:27 am

Tony all content from before the upgrade is there. Its just that new/modified content doesn't show. Permissions could well be the problem, but its extremely painful to trawl through everything with no clue of what I'm looking for.

Thanks
Jason

Paul Borgermans

Thursday 09 October 2003 5:13:57 am

Are you sure the upgrade was complete? Check the sql upgrade scripts too, and as always clear your cache.

If you are running an accelerator, stop your server, clean accelerator files (phpa: in /tmp), and start again.

hth

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Jan Borsodi

Thursday 09 October 2003 5:31:42 am

You should turn on debug, if you get any warnings or errors you will most likely know what the problem is.

Or it could be related to php accelerator as Tony mentioned, phpa is not fond of upgrades.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Jason Filby

Saturday 11 October 2003 10:18:22 am

Thanks to all that replied. At the end of the day I reverted to my 3.1 backup. Next time I'll test out an upgrade on a test installation first. Looking back, I think that something went wrong with the upgrade script.