Forum Replies Created

Viewing 15 replies - 1 through 15 (of 17 total)
  • Update:
    The OceanWP 3.1.1 update seems to have fixed the problem. Thank you…

    I have this problem on all my sites running OceanWP. There seems to be a conflict with woocommerce. If I deactivate the plugin, the site works fine with all my other plugins. When I activate woocommerce, I get a critical error warning, and the site has to load in safe mode. It says that my theme did not load properly. I can’t find the relevant site now, but one of them said something about the mini cart. If I find it again, I will get back to you with more details. Don’t know if that is the problem, only part of the problem, or only a symptom of the problem. The point is, OceanWP doesn’t work with Woocommerce at present. Backups loaded with older version of OceanWP. Not impressed by the unexpected workload…

    Thread Starter zahost

    (@zahost)

    Hi @tonyrobins

    Thank you for the quick response. After many many hours of fiddling and trying different things, I found the problem and also the solution.

    Disabling firewall was the complete opposite of what worked. I use Wordfence, and it creates some restrictive files connected to the .htaccess file. At first I tried to install only WPVivid to do the transfer which should have copied all the plugins. Turns out that Wordfence must be active first with the way my folder structure is set up. Once I set up the Wordfence plugin, everything worked a charm.

    I have no idea why the inclusion of PHP 5.6 worked somewhat, save for circumventing the redirect prevention by Wordfence. In my case it has to do with subdomains being installed in the sub-folders of my main domain which had Wordfence from the start. Had I known which files to edit or remove, the redirect error would have been sorted the first time.

    I have since tried this method on another two sites, and it worked perfect every time. They were all internal transfers, so I’m not sure if this will have an impact on moving between servers where Wordfence is active on one of them. I’m guessing that you won’t need to have Wordfence active on the target site if it is running in a different environment which doesn’t have some sort of preexisting security system managing its folders. Having different security measures on the source and target sites may be an even bigger headache.

    Your plugin is not at fault. It works beautifully. I added Wordfence to the tags, and I’ll mark this as resolved in the hope this revelation will help others in a similar situation.

    Thank you for a great plugin, and stepping up like a BOSS. You guys are awesome…

    Thread Starter zahost

    (@zahost)

    @simonskyverge I think that it quite obvious that Woocommerce is not loading the scripts completely, which suggest a conflict with your plugin, as none of the other plugins causes the behavior in question. Unfortunately, my staging environment is occupied with other work, and setting up another and cloning my site for the little benefit I’ll get out of it, is not worth the effort. Deactivating the plugin for editing purposes is the dirty workaround I’ll use. It takes up much less of my time than to try and get this resolved. If I get some more spare time, I’ll go and dig through the debug logs to see what I can find. I can’t commit to any time-frame though. I’m unsure if this topic should be marked as “resolved” in the absence of other options in the meantime, or just leave it open. Let me know how you wish to manage further exploration of this issue.

    Thread Starter zahost

    (@zahost)

    Hi @simonskyverge
    With all plugins activated, I get a “500 internal server error” in the console.

    It does not generate any additional errors by clicking on screen options. It just does nothing.

    No errors are showing when clicking on the edit product image. The popup does not load. Instead, a new page loads without errors, showing me only the ancient library interface.

    Clicking on the “Add product gallery images” link generates the following error
    Uncaught TypeError: wp.media.controller.Library is not a constructor (meta-boxes-product.min.js:1:11107)
    Nothing happens on the page itself though.

    When I deactivate the Facebook plugin, no errors show any longer and everything works as expected.

    Running only Woocommerce and Facebook for Woocommerce is not an option though. The act of deactivating plugins already caused unnecessary reworks on parts of my site. Still, I deactivated the non-essential plugins I’m willing to sacrifice, but the problem still persists with FB 4 WC. From what I can see, it only affects the product image selection and gallery as I described above, and it prevents the screen options drop-down from working. The latter is confined to the product edit page. It doesn’t affect the drop-down in the product list page. It doesn’t break anything else as far as I can tell, and it does what it is supposed to do. It just seems that it is blocking the product edit page from loading correctly.

    Thread Starter zahost

    (@zahost)

    @julieskyverge Which part/parts of the system report are you interested in? I’m not comfortable publishing the entire report on a public space.

    • This reply was modified 5 years, 7 months ago by zahost.
    Thread Starter zahost

    (@zahost)

    Hi @julieskyverge

    In my case it is only simple products, as I don’t have any variable products listed at the moment.

    @rafinkhan I’ve run a few test which previously broke my sites. Everything seems to be back to normal. The plugin is working as it did before. No hassles during or after the update. Thanks for getting on top of this so quickly and relentlessly. Now we can all sleep easy tonight…

    Bugs exterminated successfully.
    Good job!!!

    From my side, as soon as I update EA, it breaks a carousel from another plugin (JetWidgets). The EA plugin itself seems to be fine, as all the elements I’m using at the moment works after the update. Somehow the carousel can’t read the manual excerpt from posts and pulls the entire post into the widget with background image and all (this after updating EA…which is suspect). It looks like it breaks something in Elementor itself. Hence, I had to do another backup restore today after I could not fix the issues for the carousel. I updated all other plugins after restoration save for EA. Everything survived the update process with EA excluded. Due to time constraints, I can’t risk running the EA update again any time soon.

    I’ll keep an eye on new developments about this issue until I have more time to spend with it. Right now, this is robbing me of too much time.

    Hello again.

    One thing to remember is that there are several cache locations which can reproduce the results of your problem even after it was fixed.
    1. Server cache (hosting environment) Never had any trouble here
    2. Browser cache (Chrome is the worst in my opinion)
    3. Plugin cache (plugin specific like EA) a bit redundant if you ask me…
    4. WP Cache (could be a plugin for site cache)
    I would recommend the sequence 3,4,2 before checking the site.

    Depending on your setup, you may not have access to the server cache, but I’ve never had issues there (hence the skip). The results of the error could still remain in your site cache and your browser cache after you have flushed the EA cache. This error doesn’t seem to overwrite the styling, it just prevents it from being loaded. (I could be wrong here)

    Remember also to reload all pages you had open at the time of clearing any cache.

    On my other sites, I cleared the EA cache before updating the plugin. For me, this prevented those sites from breaking as well.

    At first I only cleared the EA cache (which didn’t work), and I didn’t think to clear the other caches as well, so I restored a backup. On the third restore, I cleared the EA cache before the update, and this worked for me. It is a pity that I neglected the other caches during this whole process. It might have saved me a lot of work, but I’m not rolling back anything to check this theory.

    The bottom line is that the results produced by the error could be cached elsewhere as well. It does seem that the error in the plugin’s coding is confined to the cache management only.

    It would seem this plugin runs its own cache which you must clear manually in the plugin’s settings page under the “tools” tab. I activated the plugin, cleared the cache there, and now it seems to be working. Too bad I can’t roll back now to see if my content would have stayed intact if I just knew to do this from the start. I am unimpressed by the amount of work this caused for me…

    I have the same problem as you @surewisemike. Everything is in one section, with all my styling broken. This is not the first issue with this plugin. Before, it reduced the content of the flip-box to the size of an icon. I just got a major whipping from my customers where I’m running this plugin. I have several sites to go and fix now.

    I restored a backup and got the exact same result after updating. Nothing to do with any caching. The update breaks your site the moment you activate it. I ran an update while deactivated, and everything was fine. The moment you activate, it breaks any page with elements from this plugin. No choice but to deactivate. If this is not fixed with the speed of white light, I’ll have to find an alternative…

    Thread Starter zahost

    (@zahost)

    Hi Thomas,
    Thanks for your reply.
    Yes. The URL is hard-coded in my merchant account. I’ve confirmed with PayFast support that the URL for sandbox and live deployment remains the same (https://YOURWEBSITEURL/?wc-api=WC_Gateway_PayFast) If the server is blocking the ITN, it will do so in sandbox as well. PayFast did confirm that the ITN’s were delivered successfully on the first try on all the transactions so far. It seems as if the PayFast plugin is not passing the information to woocommerce in the live deployment.

    As I was typing this reply, Rynaldo from Automattic directed me to put the following code in a snippet (or the functions.php of the child theme) which seem to have solved the order updating issue…

    add_filter( ‘woocommerce_gateway_payfast_is_valid_ip’, ‘__return_true’ );

    It seems like the PayFast URL was not validated by the system on the return of information from PayFast. The above line of code solves that.

    For anybody else having this issue:
    I pasted the line of code in a new snippet in the “Code Snippets” plugin. It can be named anything. Just paste the line and nothing else. Save and activate the snippet. I hope this helps someone else searching for days on end for a solution…

    Thread Starter zahost

    (@zahost)

    Thanks. I’ve duplicated this post there, but I will leave this one open as well for now…

    It seems to work when I visit your link. How did you manage to get it to stay open?

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