mellowvision
Forum Replies Created
-
that’s not really good news.
I agree. removing established features is not a great business practice. I really hope this isn’t an upsell to the premium package. This is going to be a huge hassle, to have to find new caching software for dozens of sites… not to mention explaining to clients why their site is running slowly all of a sudden, and how that will cost them more money for my time to update the site with new caching software. Totally unacceptable, especially with such short notice, and on a plugin that has, for a long time, promoted auto-updates.
that’s right, start a new topic, so that people don’t realize this is an issue that hasn’t been fixed in months and months. phhht. how about you guys fix it, so we don’t have to start a topic at all?
they will never fix this because it’s not an ecommerce related problem.
Forum: Plugins
In reply to: [Authorize.Net Payment Gateway WooCommerce Addon] Akamai ChangeI am looking to find the same information, but I don’t understand your reply.
Will the existing plugin be updated to support the Authorize.net required changes or not?
rolling back to the old plugin version 2.1.23 allowed me to continue having galleries with spaces in the titles, but galleries created with the broken updated plugin are still unusable, and needed to be reuploaded. it sucks to have to roll back to an old plugin, after 2 consecutive updates don’t work properly. I can’t say I’d opt to use any photocrati product again int he future… this is the fourth time in 2 years that I’ve had major problems with updates breaking functional sites. I haven’t lost so much time or money on any other plugin I’ve used on dozens of sites.
today’s update does not fix the problem. New galleries created with spaces in their names, and galleries that have been created over the past 2 weeks with spaces in their name, show a no images message instead of the gallery. you can create a gallery without a space in the name, and it will display fine.
you’re seriously going to give me a link to the where to post page?
SO insulting. get your act together and release an update already. it’s been 2 weeks.
when are you releasing a tested fix for this? manual updates to untested betas waste a lot of my time. I don’t think you understand how much money I’ve lost due to the nextgen failures over the last 2 years. so frustrating. when? that it is the only question I am interested in hearing.
also, you say it’s not a problem with the paid plugins, but we have paid plugins, and we still have this issue.
it’s been over a week. when is the new version to be released? This is ridiculous. we shouldn’t have to beta test bug fixes, nor should they take a week on a paid plugin. I regret choosing nextgen every time you guys make a major release. no other piece of software has made my work harder.
I am having this issue too on a high profile site. we really need an update quickly.
Forum: Plugins
In reply to: [WooCommerce] thank you page gone after updatesright, but it is able to use the checkout permalink throughout the process and it only fails to find that order-received permalink after the order is submitted. where is the order-received permalink variable set? does the credit processing plugin affect that?
Forum: Plugins
In reply to: [WooCommerce] thank you page gone after updatesI should add that no other pages on the site do this. the entire site operates correctly EXCEPT the one critical thank you page that woo is serving incorrectly.
Forum: Plugins
In reply to: [WooCommerce] thank you page gone after updatesthe wordpress url is set to aliceincentralpark.com/dev
the site url is set to aliceincentralpark.comthis worked until recently updating the woocommerce software. after the update is when it fell apart.
can you tell me which file in woocommerce actually determines where to direct a user after a sale is complete? woocommerce is clearly grabbing the wrong address.
Forum: Plugins
In reply to: [WooCommerce] thank you page gone after updatesunfortunately, changing the .htaccess file to reflect the dev directory does not affect the resulting thank you request, it still loads the /dev/ version.