Seems to work with no problems.

If I set the cache deletion to 12h or so, would it still work with the daily cron?

anyone have an nginx config version of the rewrite shown in the webgalli tutorial?

<IfModule mod_rewrite.c>

    RewriteEngine on

    RewriteRule .* - [E=HTTP_IF_MODIFIED_SINCE:%{HTTP:If-Modified-Since}]

</IfModule>

@krischan : the cron job removes all files older than the age you sepcify in settings. So if you set the value to 12 hours, then the cron will remove all cache files > 12hrs old.

@ura : it available by default with most of the servers. Check your network profile in chrome window to see whether you are getting a 304 header.

oh ok, i ran the test and the response was that 304 is present.. i though maybe i needed to add another line in the config to activate some aspect of this.

i am testing the new version of this plugin; thanks for updating.

i am seeing some issues with logging in/ out..

sometimes i log in or out and the notification is shown that the login/out has been successful and yet the page has not changed to reflect the login/out change.. e.g. i log out and the page refreshes and i am still viewing the logged in view of the page/site.

also strangely i am seeing that the css animation that i added to the error-state messages has moved so that it is being added to the dropdown login panel instead of the error-state messages.. so now the login panel vibrates from side to side when there is an error.. which i quite like.. lol.. but is not what i intended and i think this version of the plugin has caused this.. any idea why that might be?

thanks

so i am seeing that:

• i log-in.
• 2 notifications are shown - one that i have logged in and the 2nd says 'reloading the page'.
• then the page refreshes and i see the logged-in view of the site.
• i log-out.
• the page refreshes but i am still logged-in.
• i log-out again.
• this time i am completely logged-out.

@ura:

sometimes i log in or out and the notification is shown that the login/out has been successful and yet the page has not changed to reflect the login/out change.. e.g. i log out and the page refreshes and i am still viewing the logged in view of the page/site.

We are unable to replicate it.

also strangely i am seeing that the css animation that i added to the error-state messages has moved so that it is being added to the dropdown login panel instead of the error-state messages.. so now the login panel vibrates from side to side when there is an error.. which i quite like.. lol.. but is not what i intended and i think this version of the plugin has caused this.. any idea why that might be?

The animation is added in this version of the plugin as part of ajax form submissions. Look inside the code init_galliCache.php and you can change it as per your needs.

@Krischan : I just noticed that the plugin is enabled in your site, but the pages are not being cached. Please make sure that, you have saved the plugin's settings.

ah ok, i am glad you added the animation as i was having a tough time thinking of how the animation could have 'moved'. :)

the login issue continues some more details now i have disabled lazy_load:

• i login from the homepage
• 2 notifications are shown - one that i have logged in and the 2nd says 'reloading the page'.
• the page refreshes and i am on the main log-in page - not logged in (sometimes with an error message: 'sorry, logging in from a different domain is not permitted. please try again').
• i log in again from this page and the page reloads back to the same log-in page.
• if i now go to the homepage i see the logged in view and i am indeed logged in.

i don't know why the domain error message is shown.i think maybe there is a variable or flag not being set/read somewhere in the login logic.

@ura

i don't know why the domain error message is shown.i think maybe there is a variable or flag not being set/read somewhere in the login logic.

Your website with and without www is loading two different pages. Thats may be the reason for domain error. Use the fix from elgg docs which is in the comments section of previous version.

aha, yes; i was using faulty syntax in the nginx config file for the site. i have fixed that now and the login/logout is ok. thankyou.

i notice now that the login_redirector plugin is being bypassed so that all log-ins go to the same page the user is already viewing when they login. that's ok for me, i will just remove the login_redirector plugin.. something to notice though as others may view that as a problem for their site.

@ura:

i notice now that the login_redirector plugin is being bypassed so that all log-ins go to the same page the user is already viewing when they login. that's ok for me, i will just remove the login_redirector plugin.. something to notice though as others may view that as a problem for their site.

This you can fix by applying some logic to the ajax_form_submissions(). Since this plugin cover's whole aspects of elgg, it wont be possible to develop fixes for each and every third party plugins.

Also, please report back your performance improvement with this plugin in nginx server.

@Team Webgalli strange, I have done everything according to your tutorial and have save the settings now again. But you are right, it doesn't seem to be working.

Maybe because I am using Elgg 1.8.14?

@webgalli - ok, i think i will just leave the redirector off for now.

i don't have much traffic on my site presently.. from my own testing here i can see that pages load 50-75% faster with this cache enabled, after the first page load adds the page to the cache (when logged out).

i have noticed that when i test the site using pingdom tools page speed checker that the load time increases there by 50+% instead of decreases! i do not know why.

i found another issue..
there is a rendering glitch on the group page (owner block) which only appears when the gallicache is activated.

i am seeing that the page structure is broken and a rogue set of characters appears on the page at the bottom of the group's sidebar owner block: ");

i will see if i can locate the cause tomorrow

i located that this group glitch was caused by the interaction of group_tools and gallicache in some way.

i will let coldtrick know and see if they are interested to locate the cause.

when will this plugin be updated with no bugs please? or is it ok now?