Forum Replies Created

Viewing 15 replies - 1 through 15 (of 104 total)
  • Thread Starter NAROLLES

    (@narolles)

    Hello @pierrelannoy ,

    After multiple tests and verifications, I was able to clearly identify the root cause of the issue encountered.

    The problem was related to the CSS scope. The CSS needed to be applied at the global site level. When it was injected at a more local level (page or component level), it was being affected by the object cache mechanism, which resulted in inconsistent and unpredictable behavior on the front end.

    Once the CSS was moved to a global scope, all interference with the object cache was eliminated, and the site returned to normal, stable operation.

    Thank you for your support and assistance.

    Thread Starter NAROLLES

    (@narolles)

    Hello, @pierrelannoy

    Are you using any specific Elementor options related to CSS/JS management (e.g., external CSS or inline CSS)? External CSS as recommended by Elementor.

    • Have you disabled Elementor’s internal cache in the performance settings? YES
    • Does adding a unique WP_CACHE_KEY_SALT key to wp-config.php make any difference?

    After implementation, I can confirm that it does NOT.

    • Regarding the AI: Yes, the AI ​​helps me understand the situation and write a message in your language, but the problem is very real, and so are my responses.
    Thread Starter NAROLLES

    (@narolles)

    Hello, @pierrelannoy

    Here are the details of the hosting environment:

    • Hosting provider: PlanetHoster (HybridCloud / N0C)
    • Server type: Dedicated environment (not shared)
    • Architecture: Virtualized instance (no Docker, no Kubernetes)
    • Web server: Appache acceleration LiteSpeed
    • Operating system: Linux
    • PHP: PHP 8.4 (with OPcache enabled)
    • Object cache: APCu (via APCu Manager plugin)
      → Redis and Memcached are installed but currently disabled due to conflicts
    • CMS: WordPress
    • Page builder: Elementor (cache disabled)
    • Load balancing: No load balancer (Il y aurait CloudLinux qui pourrait balancer les ressources entre les différents compte N0C sur le serveur, toutefois, puisque vous avez un seul compte, la charge n’est pas équilibré entre ceux-ci.)
    • CDN: None (no Cloudflare or external CDN)
    • Traffic: Moderate, mostly B2B audience

      https://www.awesomescreenshot.com/image/58200787?key=e595781d1cb622b861e1f05b696ed631

      https://www.awesomescreenshot.com/image/58201042?key=6acd9ad270b48b448fb9aa7dfacd1902
    Thread Starter NAROLLES

    (@narolles)

    Hello @pierrelannoy ,
    Thank you for your reply and for taking the time to look into this.

    Of course — here is a more detailed and concrete description of what we are observing.

    The issue does not appear as a hard incompatibility or fatal error, but rather as an intermittent inconsistency in CSS rendering when APCu is enabled as an object cache in a LiteSpeed + Elementor environment.

    Observed behavior:

    • After editing and saving an Elementor page (using containers / flexbox), some container styles are not applied on the frontend.
    • The corresponding CSS files do exist on the server, but they are not consistently reflected in the rendered page.
    • Republishing the same Elementor content (without changes) temporarily fixes the issue.
    • The problem reappears later, without further content changes.

    Key diagnostic point:

    • As soon as APCu (via APCu Manager) is disabled, the issue disappears entirely.
    • The behavior is reproducible and consistent:
      Elementor + LiteSpeed cache + APCu enabled → unstable CSS
      Elementor + LiteSpeed cache + APCu disabled → stable CSS

    Elementor configuration (for clarity):

    • CSS print method: External files
    • Elementor internal cache: disabled
    • No CSS/JS minification or combination applied by LiteSpeed
    • Issue observed specifically with container-based layouts (Flexbox)

    Our conclusion so far:
    This seems related to object cache timing or stale transient data being served by APCu during Elementor’s multi-step CSS generation process, rather than a direct incompatibility with Elementor itself.

    We fully understand that this may be an edge case, but given the reproducibility and the fact that disabling APCu resolves the issue completely, we felt it was worth reporting.

    Many thanks for your support and your time.

    Best regards,
    Luc Narolles

    Thread Starter NAROLLES

    (@narolles)

    Subject: Clarification regarding the “Global Logout” button and WordPress session tokens

    Hello, Hi @joelcj91

    After further investigation on our side, we have identified the root cause of the behavior we observed regarding the “Global Logout” button displayed on some user accounts.

    This functionality is actually based on the native WordPress core session (token) management system, and not on a mechanism introduced by your plugin. The presence of this button simply depends on whether multiple active session tokens exist for a given user.

    On my side, there was therefore an initial misunderstanding, as I first assumed this behavior was coming directly from Loggedin – Limit Concurrent Sessions, whereas it is in fact a feature provided by WordPress itself.

    That being said, your plugin is still working as expected and remains very useful: it properly interacts with WordPress session tokens, especially when resetting a user’s sessions or limiting concurrent logins, which is exactly the intended effect in our use case.

    I just wanted to share this clarification with you for information.

    Thank you for your work and your support.

    Best regards,

    Thread Starter NAROLLES

    (@narolles)

    Hi @joelcj91

    The global logout button is located on the WordPress account profile page.

    I understand that it can’t be translated via a plugin but directly in the core.
    Thank you.

    Thread Starter NAROLLES

    (@narolles)

    Hello
    I am the only administrator, apart from support staff interventions.
    The list of blocked users could be used to activate, for example via an email (provided an automation plugin can handle this).
    thanks

    Thread Starter NAROLLES

    (@narolles)

    I’d like to take this opportunity to ask a follow-up question:
    1 – Would it be possible to list the users who are currently blocked for exceeding the number of active connections?
    2 – Is there a solution to perform a mass disconnection or a general disconnection for all users?

    Hello
    I second Martin’s suggestion
    what should I put in function.php to remove from the admin bar
    $wp_admin_bar->remove_node(‘updraft_admin_node’);
    this doesn’t seem to work

    Thread Starter NAROLLES

    (@narolles)

    Hi

    I follow your notice….wait and see
    now is i think correct
    thanks

    Thread Starter NAROLLES

    (@narolles)

    Ok thanks
    I understood
    so I don’t have to call the url
    https://jardinerie-animalerie-fleuriste.fr/jaf-connect/
    in admin
    but directly
    https://jardinerie-animalerie-fleuriste.fr/wp-admin/
    indeed it’s much faster
    thanks

    Thread Starter NAROLLES

    (@narolles)

    Hi hector
    Well noted – not easy when the customer wants to read the URGENT article for which he is subscribed….
    Thank you for your longevity and reliability

    Thread Starter NAROLLES

    (@narolles)

    Hi @hcabrera hector
    I reactivated the plugin but I can’t reproduce the error
    however this morning when the subscriber contacted me I was able to reproduce the problem twice at home
    it simply displayed the error wp-json without explanation and the link which when clicked sent back to the link put in my first message
    thanks

    Thread Starter NAROLLES

    (@narolles)

    @ironprogrammer

    Hello
    Thanks for your answer and I have forwarded my request to elementor.
    I try gutenberg regularly but I can’t use it pleasantly because I regularly work by the method of “copying and pasting” text coming from outside in html” and it is not very practical
    Thanks

Viewing 15 replies - 1 through 15 (of 104 total)