Joomla Login Module disappears (and every ESI module)

[AGuerrero]

Hi

Great job with litespeed. Congratulations

But in a multilanguage joomla, last version, when I activate "ESI feature", the Login Module automatically disappears from the frontend

And Yes, it is enabled "Render Login Module as ESI" ;-)

In addition, any other module that I set to "render as ESI" also disappears from the frontend.

Any ideas or solutions?

thanks

 

[Pong]

please make sure you use LiteSpeed Enterprise, not OLS. Also need to make sure joomla gzip in Joomla Global Setting disabled.

 

[AGuerrero]

Thanks for trying to help me.

Just a question, can I know if I am using LiteSpeed Enterprise or OpenLiteSpeed? or I must ask my hosting provider?

 

[Pong]

Yes, you should.
If you use VPS and manage server yourself, you can easily find by checking : cat /usr/local/lsws/VERSION

 

[AGuerrero]

Hello.
Confirmed: We are using LiteSpeed Enterprise (not OLS)

 

[Pong]

How about joomla gzip in Joomla Global Setting? disabled? If yes, maybe you log a ticket(send email to support@litespeedtech.com) with us with login details and steps to reproduce, we can take a look

 

[AGuerrero]

Thanks. Send it.

 

[Andy Badwool]

This seems to be related to the another similar issue that I found out, which is the fact that Modules that are set to NOT be displayed at all under certain conditions, won't cache correctly.

Exact steps to reproduce the issue:

- For example, set a Module to only be displayed for Access Level "Registered" users. So this means that module normally will NOT display at ALL for Guest users under normal conditions.
- Enable Litespeed Cache
- Enable Litespeed Cache for Logged-in Users
- Set the above Module to Render as ESI - Private Type. This means the module should be cached privately for each user/visitor.

Now:
- First visit a specific page as logged-in. The module will display fine. (which is ok!)
- Now visit the same page as logged-out. The module will still display (but is shouldn't display, because it's set to only be displayed for the Registered Access Level)

If you do the opposite:
- First Visit a specific page as logged-out. The module will not display. (which is ok!)
- Now visit the same page as logged-in. The module will still not display (but is should display, because it's set to be displayed for the Registered Access Level)

I also reported this issue in a ticket: #773935

 

[Pong]

will update from the ticket then.

 

[AGuerrero]

This seems to be related to the another similar issue that I found out, which is the fact that Modules that are set to NOT be displayed at all under certain conditions, won't cache correctly.

Exact steps to reproduce the issue:

- For example, set a Module to only be displayed for Access Level "Registered" users. So this means that module normally will NOT display at ALL for Guest users under normal conditions.
- Enable Litespeed Cache
- Enable Litespeed Cache for Logged-in Users
- Set the above Module to Render as ESI - Private Type. This means the module should be cached privately for each user/visitor.

Now:
- First visit a specific page as logged-in. The module will display fine. (which is ok!)
- Now visit the same page as logged-out. The module will still display (but is shouldn't display, because it's set to only be displayed for the Registered Access Level)

If you do the opposite:
- First Visit a specific page as logged-out. The module will not display. (which is ok!)
- Now visit the same page as logged-in. The module will still not display (but is should display, because it's set to be displayed for the Registered Access Level)

I also reported this issue in a ticket: #773935

Hello, in my case simply any module that I set to "render as ESI" disappears from the frontend

 

[Andy Badwool]

Hello, in my case simply any module that I set to "render as ESI" disappears from the frontend

Maybe the ESI feature is not enabled on your server? Ask your host if it is.

 

[AGuerrero]

Maybe the ESI feature is not enabled on your server? Ask your host if it is.

The hosting is Banahosting, the support is not the best... but they said that ESI module is active.

I dont know if there is a simply way to test this.

 

[Pong]

How they enable ESI on LiteSpeed? For example, on WHM/cpanel server, they will need to add the following to /etc/apache2/conf.d/includes/pre_main_global.conf

<IfModule Litespeed>

  CacheEngine on esi crawler

</IfModule>

https://www.litespeedtech.com/suppo...ommon_installation:shared-enable-individually

 

[Andy Badwool]

Hello, in my case simply any module that I set to "render as ESI" disappears from the frontend

Looks like this was indeed a bug, it was fixed in the latest package, please try it: https://github.com/litespeedtech/lscache-joomla/tree/master/package (lscache-latest.zip)

 

[Pong]

A bug has been fixed. You can upgrade/or ask your host to upgrade to LSWS 5.4.6.

 

[AGuerrero]

The update makes modules to display an error.
I am asking for the upgrade of LSWS
thank to both

 

[AGuerrero]

Upgrade completed
The error in ESI modules persists

 

[Pong]

please log a ticket with all login info and steps/url to check the errors. Also need root ssh access