Forum Replies Created

Viewing 15 replies - 16 through 30 (of 42 total)
  • Thread Starter Shaolin

    (@shaolin)

    You too mate! 🙂

    Thread Starter Shaolin

    (@shaolin)

    Ha we cross posted @axelt_me! Glad I’m not the only one affected by this. Hey now people have 2 codes that work yay!

    I’m gonna send Viva the code so they will hopefully code the thing better next time!

    Thanks though, if I hadn’t gone searching again I would have spotted your snippet which would have worked. Previous code I’d found to put in functions file didn’t work.

    • This reply was modified 5 years, 1 month ago by Shaolin.
    Thread Starter Shaolin

    (@shaolin)

    Okay, I fixed it thanks to some advice here re other plugins doing this. I had to use String Locator but it found 2 files in Viva with the session_start(); in it and I replaced with session_write_close();

    For anyone else having this issue, the files are:
    wp-content/plugins/viva-wallet-for-woocommerce/includes/class-wc-vivawallet-credentials.php on line 33

    wp-content/plugins/viva-wallet-for-woocommerce/includes/class-wc-vivawallet-helper.php on lines on lines 221 and 493

    The Site Health problem goes away if just the credentials file is changed but I played safe and changed both of them. Oh and the plugin still works ok after the changes. 🙂

    Thread Starter Shaolin

    (@shaolin)

    Well, I contacted Viva Wallet Support, because they are supposed to be the developers of the plugin.

    They just kicked it back to WordPress or Woocommerce blaming it on errors in either of those which is baloney, it is the wretched plugin that has the error. Their earlier versions managed to close their php session but I guess they didn’t test too well with recent releases of WP and Woo.

    Does anyone have any code I can input to make the thing close it’s php session? I can’t find the session start function call in any of it’s files, while there is a reference to curl, it doesn’t have any of the strings mentioned in Site Health and code I found on this forum to close the session (for other plugins that triggered the same issue) didn’t work.

    As long it is not closing it’s php session the REST API is prevented from working and I would really like to have that functioning again.

    Somebody must know what code to use to fix this as Viva are clearly not interested in doing so!

    Thread Starter Shaolin

    (@shaolin)

    Hi, hope y’all haven’t forgotten about this thread.

    FYI I downloaded an earlier version of the plugin from here in the repository and there is no issue with that one re active PHP session and REST API error. Unfortunately I couldn’t get that plugin to work properly with my version of woocommerce.

    There is also a 3rd party Viva plugin on here, that was vitually identical to the earlier official Viva one. Couldn’t get that to work either, but again no PHP or REST Api warmning for that either, so it’s exclusive to the latest official Viva Wallet plugin I downloaded from Woo’s site.

    So while the latest version of this plugin works it is not good to use because of the php problem (it caused my server resources to be restricted in the last 24hrs since I installed it (physical memory, cpu and I/O) because the site was hitting the limits. Not a lot of traffic on the site fortunately, and that restriction hasn’t happened before so I really need to get this fixed.

    Maybe others are using earlier versions with earlier versions of woo or WP, or maybe they don’t check their site health.

    I’ve searched for code to close the session but none of it worked and I can’t find that code in any of the pugins files.

    Thread Starter Shaolin

    (@shaolin)

    Hi Rynald

    Unfortunately that didn’t help, the notice is there still. I tried both Default and Legacy settings.

    As mentioned, it is there when it’s just the default theme, woocommerce and viva plugin. Oh and the server is php 7.4

    Edit: I just did a quick downgrade to php 7.3 but problem still showed up.

    • This reply was modified 5 years, 1 month ago by Shaolin.
    • This reply was modified 5 years, 1 month ago by Shaolin.
    • This reply was modified 5 years, 1 month ago by Shaolin. Reason: typos
    • This reply was modified 5 years, 1 month ago by Shaolin.
    Thread Starter Shaolin

    (@shaolin)

    Yes, I’m afraid so. I’m using Elementor and Astra and lot of plugins (WP 5.6.2 and Woo 4.9.2) Left only woo, the viva plugin and the default theme – Twenty Twenty.

    I even tried it on the staging site by installing WP 5.7 and Woo 5.10 but still the same problem. The mere activation causes it even if it isn’t actually enabled.

    I’ll go install that jquery plugin and see if that helps. Stay tuned…

    Thread Starter Shaolin

    (@shaolin)

    Thank you so much, this is very helpful!

    Thread Starter Shaolin

    (@shaolin)

    Okay thanks. I’ll be deleting the staging site anyway I’ve moved it to a seperate site so I don’t use the resources on the live.

    Thanks for all your help, I’m really happy it looks like I can use your plugin again (I tried virtually all the other ones and didn’t like them but thought I’d have to abandon yours, so all is right with my world now. Phew! 🙂

    Thanks again!

    Hey mods, can you remove my site links please or delete the thread? It was a problem that was specific to my situation so don’t think it could help anyone else reading it. Thank you.

    Thread Starter Shaolin

    (@shaolin)

    Well that’s interesting because it showed requests reduced at GTMetrix and it reported scores it is cached, and it was faster like that than without the cache being enabled!

    I have now enabled the cache, and on the plus side it is no longer acting weird with half blank pages and disappearing header. It also doesn’t seem particularly slow this time but GTMetrix says it takes 9 secs to load when previously it was around 5.4 when the cache wasn’t enabled. However I kept retesting it there and eventiually it loaded in 4.3 (3.4 using their Chrome test)

    I haven’t done anything on the site since I last spoke to you when enabling the cache made everything go haywire, and I’ve been speaking to the host to see if there is anything on the server causing it to behave this way (they said not). And yet it is now behaving, seemingly!

    I’ve checked in Microsoft Edge which was previously messed up when plugin was merely activated and that is looking fine – and cached. So I think it is working. And I got no idea how, as nothing was touched since yesterday when it wasn’t working.

    So, I’m going to risk putting it back on the live site. Yay!

    Just one thing, when I request a domain key again (I deleted it when I had to delete all trace of it before reinstalling) will it re-optimise images. The thumbs have all been regenerated and changed sizes with the new theme, am I going to run into another issue?

    (and how do I remove the site links from this page, we just had to increase the CPU as it was hitting it’s limits so don’t want people who may be reading this thread to click it and suck up resources. 🙂

    Thread Starter Shaolin

    (@shaolin)

    Hi

    You told me to put it on a staging site, which I assumed would be better than a screenshot.

    As per the link above https://www.zellyuk.co.uk/staging you will SEE the pages are showing as cached when it isn’t enabled. And yes, everything has been purged and reset multiple times.

    • This reply was modified 5 years, 8 months ago by Shaolin.
    Thread Starter Shaolin

    (@shaolin)

    Yes, it says at the bottom of the pages it is cached by Litespeed. Regardless of whether I am logged in or out.

    Check the staging site and see. The cache is not actually enabled though. The cache status page also confirms that all the caches (private,public, object etc) ar OFF. And yet, it is caching and reducing queries according to GTMetrix, but the page is slower than without the plugin activated..

    • This reply was modified 5 years, 8 months ago by Shaolin.
    Thread Starter Shaolin

    (@shaolin)

    Hi
    There is something really odd here. Even though the cache is NOT enabled it is showing in the page source as cached. GTMetrix also acts as if it is cached. It is not particularly fast loading 5.3s 71 (requests down from 117). Without a cache on it showed 3.2 secs and 112 requests.

    I was able to put all the js and css minifies back and still worked except it was slow, but remember the cache isn’t actually on. Then I switched it on and GTMetrix acted as if it wasn’t on (114 requests, 9.4 pageload). And then the catergories and menu vanished again.

    Ended up resetting to the defaults again, disabled cache, everything worked, enabled js combined and minify and again everything worked. Not tried the CSS again yet but I suspect they’d work. Checked the pages and it shows it has been cached, GTMetrix thinks it’s cached but it IS NOT enabled and shouldn’t be cacheing.

    • This reply was modified 5 years, 8 months ago by Shaolin.
    Thread Starter Shaolin

    (@shaolin)

    On it…

    Thread Starter Shaolin

    (@shaolin)

    Yay! That got everything to work as it should normally!

Viewing 15 replies - 16 through 30 (of 42 total)