Upgrade Error 5.3.0 to 5.3.1.1

Permalink
I Upgraded recently to 5.3.1.1 and since have been unable to use the File manager.

First it would not see any of the files previously uploaded and the interface was a little messed up (still is see attached).

I tried refreshing each file but still no luck, and it throws back that it cannot find the file. I cannot delete files or upload new ones.

I tried re-installing but still no luck.

Please see attached and would appreciate any help you guys can give?

Is there maybe a database clearance issue or some file that I should have uploaded as well as the concrete folder when upgrading?

Thanks in advance
Paul

2 Attachments

craftyCS
 
craftyCS replied on at Permalink Reply
craftyCS
Just wondered if anyone was listening in on this part of the forum as the other sections seem to yield a swifter response?
katz515 replied on at Permalink Reply
katz515
You might have done..

Did you clear the site cache, and re-scan the entire files?
craftyCS replied on at Permalink Reply
craftyCS
It's strange as you can see from the screenshots there seems to be something wrong on the install. I cleared the cache and tried to rescan none of the original files could be found. So I deleted the original files and tried re-uploading a new file it appears in list but without an image preview (just the usual replacement image icon) I then I try to re-scan and it says it can't find it. It is like the image directory on my install is not being found or it is uploading to the wrong location.
Remo replied on at Permalink Reply
Remo
I guess you're also overriding some standard html elements in your css file..

if you do such things:
input {width:100px;}
div {float:left}
span {clear:both}
a {color:white}


you'll have some problems for sure..

just a guess.. Not sure if it's really related to your problem but it looks a bit odd to me...
craftyCS replied on at Permalink Reply
craftyCS
I don't understand how my CSS file is effecting the files not being found let alone the presentation of the C5 interface?
ScottC replied on at Permalink Reply
ScottC
it usually starts with ccm or something of that sort. Any "body" tag css attributes run the risk of being picked up by the DOM and applied to certain text elements and various other misc elements throughout the concrete5 ui since everything cascades down from the body of the page.

A general rule is any font color tag on the css body is a big no-no :), I am sure there are others as remo mentioned above.
Remo replied on at Permalink Reply
Remo
sorry had a bad moment.. (:

It thought you've been in the "in-site edit" mode. You can select a file from the file manager too there...

It doesn't in your case though
craftyCS replied on at Permalink Reply
craftyCS
Does this CSS issue cause my files to not be found then? as it's simple enough to change hte CSS but I fail to see how this stops the files being found?
craftyCS replied on at Permalink Reply
craftyCS
I am really hoping this is a temporary and single site issue as I would like to upgrade my client sites to the newer version but am unwilling to take the risk till I know the solution to the above problem.
has anyone please seen this before?

thanks in advance
craftycs
craftyCS replied on at Permalink Reply
craftyCS
please read above and look at the screen shots as I am still having the same issue... even on a re-installation of the upgrade.

Would really appreciate it.

cheers
Paul
frz replied on at Permalink Reply
frz
It looks to me that you do have some css issues going on.. one of several things could be happening:

1) your install is not complete. perhaps your archive got corrupted, perhaps FTP died on some file upload, it sounds like you've tried several times so thats unlikely.

2) your sites CSS is getting in the way. this doesn't make a whole lot of sense to me because you're in the dashboard, not the front end which would include your theme's specific CSS.. but who knows - perhaps you've made some other change that is calling legacy CSS somehow.. some 3rd party tracking code that shows up everywhere and overwrites common entity styles.. who knows, again strange if that's the cause

3) you simply need to clear browser cache - that'd be awesome, but certainly if you haven't cleared browser cache you should after any upgrade. same is true for site cache, if you haven't cleared it you should.

4) you are using some browser we don't develop for.

any other possible options people? anyone experience something similar?
craftyCS replied on at Permalink Reply
craftyCS
Hi thanks for the in depth response!..
Obviously at the moment I am using a slightly modified version of the simplified theme.. I will try switching to a standard theme temporarily.

In the meantime while I was attempting to switch the site cache on (enable) in the dashboards site wide settings and it will not allow me to do so, it keeps flicking back to disabled could this be related to the caching issue you mentioned?

I did have a google analytics code placed in the tracking code window so have removed this to test (it never worked at the moment anyways as I think I need to add soemthing to the bottom of the footer?).

your help is appreciated
Paul
craftyCS replied on at Permalink Reply
craftyCS
While switching my theme this appeared:

Warning: opendir(/hsphere/local/home/bloksoli/itsnotrocketscience.com/files/cache_objects): failed to open dir: No such file or directory in /hsphere/local/home/bloksoli/itsnotrocketscience.com/concrete/libraries/cache/default.php on line 130 Warning: fopen(/hsphere/local/home/bloksoli/itsnotrocketscience.com/files/cache_objects/object_2e4c689d261d629f062b0169fc7f10c7): failed to open stream: No such file or directory in /hsphere/local/home/bloksoli/itsnotrocketscience.com/concrete/libraries/cache/default.php on line 42 Warning: fputs(): supplied argument is not a valid stream resource in /hsphere/local/home/bloksoli/itsnotrocketscience.com/concrete/libraries/cache/default.php on line 43 Warning: fclose(): supplied argument is not a valid stream resource in /hsphere/local/home/bloksoli/itsnotrocketscience.com/concrete/libraries/cache/default.php on line 44.

any ideas?