Maxigallery and 0.95

Hi Doze,

have you tested the gallery with 0.95 yet? If I click on "manage pictures" something loads but the page remains as before (with only the button), no management...

Thx in advance,
Marc

I haven’t but others have and it should work ok.. You are running it uncached, yes? Maybe obvious for you, but just checking..

Yes, uncached:



beta5 rev 1631

If I click on the manage-button, something loads, but nothing shows up...

edit: Sorry, the page was cacheable, without it works... Thx a lot!

I have installed maxi with beta 5, everything seems to work well, however... Sometimes the photos dont load up... Just a blank screen... Ive tested this on different pcs and out about 5, 2 didnt load up the gallery... Logged in or not.. running maxi as [! !]

You have to run it cached ([[ ... ]]) and tick out the point "cacheable" under "page settings" of that document.

Just thought I’d mention another reason that this sort of thing can happen that was making me scratch my head a bit. If you have a hard-coded base href tag in your document head and you have multiple domain names on your server, you have to login to the manager using the exact same domain name as your base href tag. Otherwise when the form is submitted it doesn’t realize that you are authenticated.

For example, if you have the domain names blah.com and blah.net, and your base href tag specifies "www.blah.com", you can’t manage your images if you login to the manager using "www.blah.net/manager" or "blah.com/manager". I’m not sure if this would always be the case on all servers, but on the ones I’ve tested after clicking the manage pictures button (in the manager preview window) you get a regular MaxiGallery page (no form at all). You could get around this by using site_url in your base href tag, or by always logging in to the manager using the same domain name as your base href tag.

It seems obvious to me now, but it took me a while to realize why this was happening so I thought I’d share.

Even without a hardcoded base tag (i.e. <base href="[(site_url)]" />), or without a base tag at all, whatever url you access your site with, unless it is redirected before MODx handles the request, will the be the url used to initiate your php session. This is pretty much universal AFAIK and can actually be useful when testing things, but reinforces the need to be accurate and consistent with your relative paths in MODx, otherwise, you may be loading resources with two different sessions.