Back end not showing full information

To manually clean cache you should access to your server with a ftp client, like Filezilla.
Or you could do it with your hosting file manager...
But if you have never done it I think it's better if you ask your friend.

If you want to do it inside MODX actually you can: you have to use tab "FILES" top-left corner, then look for core/cache and inside cache remove directory.

But, again, if you have never done anything like this, I REALLY SUGGEST you to ask your friend
if you delete the wrong file you can "break" your site!!

No, flushing permissions is an entirely different operation. I see that you do have the files tab available in your resource tree area. Click that tab, and you will see all the site's folders and files.

Using FTP to clear the core/cache folder is a long and time consuming action. Blech!

The file manager in your server's control panel is much faster, and alternately deleting the cache folder in the files tab is also nice and fast. Although like mentioned, and as I warned about in my original post, it can be a little on the dangerous side if one deletes the wrong files/folder.

I believe the Clear Cache snippet is likely the safest option in this situation. It works nicely and won't delete anything that it shouldn't.

I'm not seeing a progress bar or a run switch, where do I activate it?



cheers

tillilab yes - I don't want to risk anything especially as he's done a lot of this work for very little!

I'm pretty sure that he had said clearing the cache was one of the first thing's he tried to test as well... hmm. It's very confusing why it works on one but not another then it works on his chrome not mine etc...

How do, just thought some of you might be interested in hearing what the solution to this problem was...

Instead of logging in with blahblahblah.com/manager I logged in with www.blahblahblah.com/manager

I have no idea why this worked! My mate told me to do it, he doesn't know why it worked either... anyone know? odd

You need to uncomment the section of the .htaccess file in the MODX root that forces the login to www or non-www (uncomment one section or the other, but not both).

Without doing that, users under www are in a different session than non-www users. Any links that take the person from on to the other will mean MODX will lose all session data.

You should also make sure there are no hard-coded links on the site, all links should be in the form of link tags containing the ID of the resource being linked to:

I actually ran into this www Chrome login issue just a few days ago. On a site that does not have any forcing rules un-commented in the .htaccess. Client got a new (used) laptop, was using Chrome, and could not log in. Removing www. got it sorted for her login purposes, but I don't wish to un-comment the www forcing line in .htaccess at all.

What else could prevent www. for the manager in Chrome? www.site.com works fine in Firefox. There's no .htaccess in the manager folder.

This particular site was just updated from 2.2.8 to 2.2.10-pl.

You could uncomment the other section that forces non-www. Using either section has no effect on users, since they can still come in on either one, it just gets translated for them. I suspect that search engines treat them as equivalent, so it wouldn't have any affect on SEO either.

And if you want friendly URLs, you definitely need the .htaccess file. If you don't want friendly URLs, you could comment out that part of the .htaccess file and just use the www translation part.