Upgrade from 5.2.1 to 5.3 - No SiteMap and No Editing

Permalink
I upgraded to 5.3, but now when I click on Sitemap none displays. When I do a search on that page, I get raw delimited text.

I also cannot edit any pages. I go to the page, click on edit, but when I click in a block, no options (ie. edit) display. It won't let me add anything to the block either.

 
virgiltu replied on at Permalink Reply
virgiltu
i found to have the same problem if using some custom templates. Not all.
DigiDoc replied on at Permalink Reply
I restarted the Firefox 3.0.8 browser and it works, but it's buggy.

Note: When I upgraded it was apparent that not everything was in place - most likely a cache problem I presume. I noticed after the upgrade that the new C5 logo wasn't there, however some other features were.

When I go to sign in, the login screen works, but then the Dashboard page is blank (when I "View Source" it's blank). If I refresh the page, it's fine.

I agree, it seems to happen more on a custom template then it does on the Plain Yogurt Template.

When I go to edit a page, it's sometimes blank like the Dashboard, however a page refresh fixes it.

I've switched back to the Plain Yogurt template and it is a little better, but I keep having to refresh a page now and then because it's blank. The last few edits were fine though.

I created a simple HTML Block, and the first time it just disappeared.

I created an RSS block, and it didn't appear in edit mode, but appeared after I saved the page. On another page I did the same thing and it worked as expected.

All in all, everything is working, but it's buggy. I'll play around with it more and compare some templates, as I suspect they could be part (if not all) of the problem. I presume that since this is not a major release, any C5 template should work as expected.

I REALLY want to use C5, but am uncomfortable about it's stability. I'm using it now on a test site, but not confident with it yet to use in a production environment for clients.
frz replied on at Permalink Reply
frz
this is odd and not the behavior I or many other folk are getting. I think something may be off on your site cache.

5.3 is in fact a major release version for us, 5.3.1 will be coming out in the coming weeks to address some of the issues that are emerging, but 5.3 has been months in development and represents a complete rework of parts of the system. I believe the update notes were reasonably clear about that.

Can you verify that your cache directories are properly permissioned? What else might be unique about your server setup? Do you experience the same issues on our demo server? Http://getconcrete5.com/demo

thx
DigiDoc replied on at Permalink Reply
I've decided to do a clean install from scratch.

So far (almost) no problems. I've got a problem with Page Types now - I just made a separate post on that issue (it only gives pages with a right sidebar regardless of what you select).

I'm trying to use C5 as-is without hacking into it. I'd much rather resolve issues here and see them fixed in the next release (if appropriate).

BTW- Thanks for the FAST responses. This is great support for an Open Source Product. I'm a Big Fan!
tmagee replied on at Permalink Reply
tmagee
I had the same issue with my site, but added the 'execute' right using cyberduck to all the site/files/cache and cache_objects and that fixed it. I'm doubtlessly a bull in a china shop on this particular move, but it worked.
katz515 replied on at Permalink Reply
katz515
I had the same problem.

And soon after I clear my cache of my browser (IE, Firefox, or Safari), it started working again.

I wrote a step by step installation guide.

http://www.concrete5.org/community/forums/installation/upgrading_5_...
ScottC replied on at Permalink Reply
ScottC
while the js script names didn't change, the version of the jquery included in fact did.

It went from 1.2.6 to 1.3.2 and ui to 1.7 something.

So that is pretty much it.
katz515 replied on at Permalink Reply
katz515
OK.

I got it.. Thanks Scott.

Anyway, all you have to do is to clear the cache of your browser.

I'm going to explain why you have to do this.

But you don't really have to read.

------

So what happened is... your browser, such as Internet Explorer, Firefox and Safari save the data on your computer by default so that you don't have to download it again from internet server.

And the old version of jQuery and jQuery UI are saved in your computer.

When you upgrade your concrete5, jQuery and jQuery UI is updated to the new version.

And concrete5.3 uses the code based on the new version of jQuery.

However, because the file name didn't change... your internet browser thinks that you are still using old version of jQuery.

That's when the problem happens.

---

Thanks Scott, I didn't know the reason why.... but it made my sense now~!
walkermacy replied on at Permalink Reply
walkermacy
yup, this fixed the problem for me! upgrading from 5.2.1 to 5.3.2 and no sitemap.

thanks a million, now i can get on to other stuff!