Forum Replies Created

Viewing 15 replies - 1 through 15 (of 63 total)
  • Thread Starter King Ding

    (@dazzerr)

    Just reporting here with the solution.

    The User Role did not exist for the User Account. A User Role is necessary in order for LiteSpeed Cache to deliver the _lscache_vary cookie when logged in. If the User does not have a Role, then this cookie is not delivered and thus logged in users will continue to see logged out webpages.

    Thread Starter King Ding

    (@dazzerr)

    Thanks. I have sent the email. I will report here for others once we find a solution.

    Thread Starter King Ding

    (@dazzerr)

    Yes. I added it to fix the problem, but that did not fix it. It didn’t make it any worse either.

    Thread Starter King Ding

    (@dazzerr)

    Yes.

    On the site in question with the issue, I have disabled all plugins and am using a 202* theme. The issue still occurs.

    Thread Starter King Ding

    (@dazzerr)

    This does not help unfortunately. I already mentioned that I have tested with all settings OFF.

    So far what does work is:

    • Disabling the plugin
    • Disabling LiteSpeed Cache from my Web Control Panel (xCloud)

    I have tested the exact same configuration on two of my other sites, and I am not able to reproduce the issue elsewhere. It seems that this is site-specific. I even migrated the Site to a fresh instance, but the issue still remains.

    I’d like to think that we can rule out the plugin being the issue. Perhaps there’s another configuration file, or server-side file that I should check?

    Thread Starter King Ding

    (@dazzerr)

    Yep, I can confirm that I have tested with the Twenty Twenty Five theme, and the issue still occurs.

    After activating the Theme, I cleared the entire cache, and I still get x-litespeed-cache: hit despite all plugin options set to OFF. 😓

    Thread Starter King Ding

    (@dazzerr)

    I figured that logged in users should not be cached by default. Hence this is rather strange behaviour.

    The other optimisation plugin is “Perfmatters” yes. I have disabled this plugin and it has no effect on the issue.

    Since deactivating this plugin, I also deactivated your plugin, reactivated it, and ALL settings are OFF across the plugin. I also emptied the Cache from the Toolbox. Despite that, I’m still getting x-litespeed-cache: hit, which baffles me because the cache is set to OFF.

    I would like to note that I am also using QUIC.cloud CDN with LiteSpeed, however the CDN is completely bypassed and “Enable Cache” + “Auto Browser Cache” are OFF in the QUIC.Cloud settings. DNS is set in Cloudflare, and is not Proxied.

    Thread Starter King Ding

    (@dazzerr)

    I used the built in wordpress import/export tool instead, and this seemed to have worked. All reviews are back and have all the relevant meta data. Hopefully this won’t be an issue again here forth.

    Thanks for your guidance, and for making such a feature rich plugin with all the tools!

    Thread Starter King Ding

    (@dazzerr)

    Thanks for the information Paul. Unfortunately Step 1 fails me right away with an error 🥲

    WordPress version 6.8.2

    Active theme: Bricks Child Theme (version 1.1)

    Current plugin: Site Reviews (version 7.2.13)

    PHP version 8.3.23

    Error Details

    =============

    An error of type E_ERROR was caused in line 376 of the file /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-content/plugins/site-reviews/vendors/thephpleague/csv/Stream.php. Error message: Uncaught Error: Call to undefined function fpassthru() in /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-content/plugins/site-reviews/vendors/thephpleague/csv/Stream.php:376

    Stack trace:

    #0 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-content/plugins/site-reviews/vendors/thephpleague/csv/AbstractCsv.php(332): GeminiLabs\League\Csv\Stream->fpassthru()

    #1 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-content/plugins/site-reviews/plugin/Commands/ExportReviews.php(47): GeminiLabs\League\Csv\AbstractCsv->output()

    #2 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-content/plugins/site-reviews/plugin/Controllers/AbstractController.php(32): GeminiLabs\SiteReviews\Commands\ExportReviews->handle()

    #3 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-content/plugins/site-reviews/plugin/Controllers/ToolsController.php(133): GeminiLabs\SiteReviews\Controllers\AbstractController->execute()

    #4 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-includes/class-wp-hook.php(324): GeminiLabs\SiteReviews\Controllers\ToolsController->exportReviews()

    #5 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

    #6 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-includes/plugin.php(565): WP_Hook->do_action()

    #7 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-content/plugins/site-reviews/plugin/Plugin.php(89): do_action_ref_array()

    #8 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-content/plugins/site-reviews/plugin/Router.php(195): GeminiLabs\SiteReviews\Application->action()

    #9 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-content/plugins/site-reviews/plugin/Router.php(52): GeminiLabs\SiteReviews\Router->post()

    #10 [internal function]: GeminiLabs\SiteReviews\Router->routeAdminPostRequest()

    #11 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-content/plugins/site-reviews/plugin/HookProxy.php(24): call_user_func_array()

    #12 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-includes/class-wp-hook.php(324): GeminiLabs\SiteReviews\Router::GeminiLabs\SiteReviews\{closure}()

    #13 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

    #14 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()

    #15 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-admin/admin.php(176): do_action()

    #16 /home/1234567.cloudwaysapps.com/lolmydb/public_html/wp-admin/edit.php(10): require_once('...')

    #17 {main}

    thrown
    Thread Starter King Ding

    (@dazzerr)

    1. 25
    2. I would think you might know better than anyone? I presume that the main review post would stay in wp_posts. Perhaps your plugin generates new meta and glsr table data from that if I were to delete/recreate each of the glsr tables?
    3. No, wp_glsr_assigned_posts has data as shown in the screenshot here: https://share.cleanshot.com/bCJfWSNW . wp_glsr_assigned_users is empty.
    4. Nope.

    Thanks!

    Thread Starter King Ding

    (@dazzerr)

    Thanks for the quick reply. I’ve not imported the database rom a backup or another site. I’ve been using the plugin for a long while now, and the only thing that has changed is plugin updates across the site.

    Unfortunately deactivating and reactivating doesn’t work for me. It’s likely broken foreign index keys. Could you guide me on how to fix that?

    Thread Starter King Ding

    (@dazzerr)

    I did some more analysis across the glsr tables and noticed some anomalies here…

    wp_glsr_assigned_posts: https://share.cleanshot.com/bCJfWSNW

    wp_glsr_ratings: https://share.cleanshot.com/vG4hpH3g

    When I create a new review in the backend, this is what happens in the database:

    • New row is created in wp_glsr_ratings with the ID column set to 0.
    • No new row is created inside the wp_glsr_assigned_posts table.
    • New correct row is created in wp_posts.
    • New rows in wp_postmeta: https://share.cleanshot.com/mprzFJHf

    I notice that for working reviews, there is a serialised meta_value with the meta_key_submitted“: https://share.cleanshot.com/tSTvyt2y. So I would expect new reviews to have this post meta, but they don’t.

    So I am wondering why post meta is missing for new posts? Perhaps this has a knock on effect to why there is no new row created in wp_glsr_assigned_posts?

    I also notice this error in my log:

    [2025-07-27 00:28:36] ERROR [Database:216] Can't create table loldbtable.wp_glsr_assigned_posts (errno: 150 "Foreign key constraint is incorrectly formed")
    [2025-07-27 00:28:36] ERROR [Database:216] Can't create table loldbtable.wp_glsr_assigned_terms (errno: 150 "Foreign key constraint is incorrectly formed")
    [2025-07-27 00:28:36] ERROR [Database:216] Can't create table loldtable.wp_glsr_assigned_users (errno: 150 "Foreign key constraint is incorrectly formed")

    Here’s the database row types for reference: https://share.cleanshot.com/rg42LDTf & https://share.cleanshot.com/Zf7XtgNH & https://share.cleanshot.com/f0VNf1Fm

    • This reply was modified 10 months, 1 week ago by King Ding.
    • This reply was modified 10 months, 1 week ago by King Ding.
    • This reply was modified 10 months, 1 week ago by King Ding.
    • This reply was modified 10 months, 1 week ago by James Huff.
    Thread Starter King Ding

    (@dazzerr)

    I’ve tried these tools and unfortunately they don’t fix the issue. I’ve also checked the Database manually, and I notice nothing strange. I’ve compared a working review to one of the ones that are not working, and I don’t notice any concerning differences. I looked in wp_posts and wp_postmeta. The wp_posts I compared (same post_id reviewed) have the same data. wp_postmeta too. Here’s that comparison: https://share.cleanshot.com/MLgrztGp vs https://share.cleanshot.com/fswvScsK . You’ll also see that they look the same. Is there anywhere else in the database I should look to compare? I’m a bit lost on what to do or what the problem could be here. Even when I manually create a review, it doesn’t seem to save the right in the admin backend?

    Thread Starter King Ding

    (@dazzerr)

    Thanks for acknowledging this bug. I look forward to a fix 🙏

    Thread Starter King Ding

    (@dazzerr)

    Given these settings (https://imgur.com/7GX7Tdu), I would assume that Apple Pay payments would be rejected because usernames are set to not auto generate?

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