Unable to view filesystem in tree

I have several sites running revo 2.2.4, php 5.3.19 on linux. The sites were running fine until my server php was upgraded from 5.2.? to 5.3.19. My folders are chmod 755 and files 644. Now no one can view the filesystem files in the tree. When the page loads, the triangle shows for a second then disappears.

I have upgraded one of the sites to revo 2.2.6 (my clients site) but no change. I have cleared the cache manually. I have run the setup multiple times. I have tried all of the suggestions in other threads but nothing is working.

Can anyone help?

I think php 5.3 does something with slashes. Did you check the filesystem properties [basePath and baseUrl in your Media Sources?

Thanks for replying to my post.

I have checked them. Nothing has ever been in those fields and everything worked fine. I put a slash in there but nothing has changed.

I am stumped. Nothing I tried has fixed this issue and there is no way I found to export my resources.

When I did a fresh install on the same server with the php 5.3.19, everything works great, like its supposed to. I really like Modx but I dont want to take a chance with my clients sites that this could continue to happen without a fix.

If PHP was updated... is it possible that something with Apache (?) was updated? E.g. if the user/group that Apache runs as, or if the PHP modules like suexec were changed, then the Ajax requests that get data for the filesystem might fail, and you end up being unable to see them in the file system. Just a thought.

Go to your manager login and view the page source. Go down the list of links in the head and click each one. See if any of them come back with a 403 or similar. If one, or several, do then that should narrow down where the problem is.

Quote from: lchestnut at Jan 24, 2013, 07:42 PM

I really like Modx but I dont want to take a chance with my clients sites that this could continue to happen without a fix.

Any CMS is going to have some small glitches. Don't be so quick to give up on MODX it's by far the best available.

It sounds like a file ownership problem, rather than a permission issue (unless the host was using suExec or suPHP or something similar and has stopped doing that).

Glitches happen, and MODX is not glitch-free. My advice is that if you've built out a highly-customized site and you don't have a support agreement or a retainer with this client DO NOT EVER UPDATE ANYTHING ON IT OR ON THE SERVER EVER. I know that's not good from a security standpoint, but you gotta make sure you can cover the maintenance time involved for updates. Updating PHP can make LOTS of things explode -- it's super dangerous to do that. More typically, you'd have identical dev/prod servers and you'd test everything 10x on the dev server before pushing it live on prod.

Quote from: eric.swd at Jan 24, 2013, 11:50 PM

Go to your manager login and view the page source. Go down the list of links in the head and click each one. See if any of them come back with a 403 or similar. If one, or several, do then that should narrow down where the problem is.

None of the links came back with an error.

Quote from: eric.swd at Jan 24, 2013, 11:50 PM

Any CMS is going to have some small glitches. Don't be so quick to give up on MODX it's by far the best available.

I agree with you. Modx has given me more flexibility etc. than any other CMS out there. I am just a little frustrated right now.

Thanks for your suggestion.

Quote from: Everettg_99 at Jan 24, 2013, 10:14 PM

If PHP was updated... is it possible that something with Apache (?) was updated? E.g. if the user/group that Apache runs as, or if the PHP modules like suexec were changed, then the Ajax requests that get data for the filesystem might fail, and you end up being unable to see them in the file system. Just a thought.

Quote from: BobRay at Jan 25, 2013, 12:20 AM

It sounds like a file ownership problem, rather than a permission issue (unless the host was using suExec or suPHP or something similar and has stopped doing that).

I will double check to see if Apache changed. I user/group has not changed though. I will check to see if any of the modules changed. Funny, when I do a fresh install of the same version of Modx, everything works as expected.

Quote from: Everettg_99 at Jan 25, 2013, 01:06 AM

Glitches happen, and MODX is not glitch-free. My advice is that if you've built out a highly-customized site and you don't have a support agreement or a retainer with this client DO NOT EVER UPDATE ANYTHING ON IT OR ON THE SERVER EVER. I know that's not good from a security standpoint, but you gotta make sure you can cover the maintenance time involved for updates. Updating PHP can make LOTS of things explode -- it's super dangerous to do that. More typically, you'd have identical dev/prod servers and you'd test everything 10x on the dev server before pushing it live on prod.

I will definitely keep this advice in mind. I am still a work in progress.

Thanks to you all.

I will check these things out and keep moving forward with Modx. I do love it.

Lisa

You may want to re-run the setup script on your problematic install -- that can often clean up a lot of little bugs. Although, I was having problems running the 2.2.6 setup script for this "trouble-fixing" scenario...

I was just about to post a new thread about what I believe is the same problem. I have never seen this on any of my installs of Modx. This time an IT person for the company that I'm designing a site for, setup ModX 2.2.5 on a new hosting server. I don't know where he is hosting it, but I do know it's ModX 2.2.5 and it was a fresh install. All is working fine except clients can't add photos to file system and they can't view the file tree as mentioned above. I see the arrow next to the media folder, but when I touch it with the mouse, it disappears.

I've checked all of the permissions and they are identical to all of my other ModX 2.2.5 installs.

We're getting ready to launch the site, but the client can't add images. We are completely stuck.

Doesn't look like any answer here has helped yet.