paradime
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] Checkout total and new order total don’t matchSorry for the delay in getting back to you. The issue started since the initial store setup. We just didn’t realize until the first review orders started coming through.
I’ve already attached the System Status Report. Your colleague said, “Thank you for sharing the system status report. Everything appears to be working fine based on the report.”
Also, the site is not using Flat Rate. We’re using the following plugin to calculate shipping:
WooCommerce Canada Post Webservice Method
https://truemedia.ca/plugins/cpwebservice/
I consulted with him and in the end, he stated:
“…this could be a Woocommerce bug.”Forum: Plugins
In reply to: [WooCommerce] Checkout total and new order total don’t matchI’ve uploaded the screenshot to my Google Drive. I hope that’s OK:
https://drive.google.com/drive/folders/1Uw1_0KbDNdBeI0Hm0G1_zuC7MpicZHmpAs you can see, the tax amounts are different because it’s not being applied to the shipping.
Forum: Plugins
In reply to: [WooCommerce] Checkout total and new order total don’t matchI appreciate any help you can offer. I don’t see any fatal errors but here is the log:
https://gist.github.com/paradimeinc/7e6fc783f089ed17cb1e952c0a779e55
The bug affects all orders. Again, taxes on shipping are correctly calculated and added to the total at checkout and billed. However, the invoice generated by Woo doesn’t include the shipping tax, therefore making the total wrong. It doesn’t match the invoice sent from the payment processor.It doesn’t seem correct that my client are upset that their galleries haven’t been broken and we’re coming up on 2 weeks. They’re blaming me and expecting me to fix it but NextGen is effectively outside my control.
I appreciate the fix and v2.2.20 seem to be working.
I’ll update this review once v2.2.20 is provided as an update within WordPress.
I think you’re right. This PHP issue continues a week and 1/2 after it was first reported and no updates or fixes.
I’ve lost all confidence with Imagely and working on removing it from all my client sites. When the various Imagely subscriptions come up for renewal, we will be cancelling and advising our clients to do the same.
I appreciate your replies here and on other threads.
I should mention that on some sites, we used Nextcellent and it’s working perfectly. Strange how Nextcellent works but NextGen breaks.
Regardless, my phone has been ringing consistently over the past 2-3 days with clients upset, rightful so, that their galleries are gone.
Some have demanded an immediate switch to a different solution and the rest are quickly growing impatient. After all, this has now being going on for about a week.
The longer this drags on, the more likely we’re all going to abandon NextGen completely and our subscriptions with Imagely. Therefore, it’s important that an update/patch is provided ASAP.
Once I start the work in moving them away from NextGen, there’s no coming back.
v2.2.10 didn’t work for me. Upon activation, it immediately crashed a test site I tried it on.
I’m not sure how much longer we’ll have to wait for a patch. An ETA would be nice. Today? Tomorrow? End of the week?
While I recognize this isn’t completely the dev’s fault, I’m being forced to start the process of migrating sites away from NextGen and cancelling subscriptions.
Sorry, it works. The problem was that the directory had some WordPress folders. Once I delete everything including the .htaccess file, it all worked.
Forum: Plugins
In reply to: [Contact Form 7] Reply-To: [your-email] – no longer workingI think maybe what he’s saying is that Reply-To: [your-email] no longer validates.
It’s strange because on some of my sites, Reply-To: [your-email] validates and on others, it doesn’t, even though I’m running the same version of the plugin. Should it be Reply-To: <[your-email]> ?
Honestly, this recent update has been a nightmare for me and I know for many others. Forms that worked fine before no longer work.
Hi Everyone,
I wanted to post a quick update here. Unfortunately, there wasn’t enough of a response to justify creating a fork.
The good news is, this plugin seems to be working great even with WP 4.2. Hopefully it will continue to work and give people enough time to transition away.
From my perspective, I’m closing the door on FireStorm for good. Maybe someone else will pick it up and carry it forward.
Forum: Plugins
In reply to: [Unyson] Mega Menu?Mega Menu seems to only work with those themes that specifically take advantage of it.
Try using their Scratch theme as an example:
A few things I can suggest:
1) Make sure you’re running FireStorm 2.7.11.
2) Sometime after a WP update, it asks you to do a database update as well. Make sure you fo that.
3) Make sure you’re running a newer version of PHP (such as 5.4).
4) Check this thread:
5) Check previous support threads for this error and hopefully a solution.
I can confirm that the free (non-Pro) version works great with both WordPress 4.0 and 4.1.
Hi Everyone,
I just wanted to mentioned that I did some quick Google searches and it appears that the author of this plugin passed away back in Jan 2014.
If confirmed, it’s very sad and also explains why there haven’t been any updates as well as the current state of his various web sites.
Hi Everyone, if people would like to contact me directly, please e-mail [ redacted, support is not offered via email, Skype, IM etc. only in the forums ] (trying to avoid spam), I’ll contact you with my company information and we can take it from there.
What changes, updates or bugfixes are you looking for specifically? Certainly contact me and we can take it from there but also post your issues here to see if others are experiencing the same problems.