-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Your API credentials are invalid #80
Comments
It looks like they just ignore this one. I'm having the same thing on a production site, and losing sales. |
My client is thrilled. I am a big fan of writing bad reviews. |
Both of you are having problems after updating the plugin? Have you tried reverting to the last working version of the plugin? Obviously not a solution, but would prevent loss of sales in the meantime. |
I ended up reverting to the old one. Everything is good for now. Would love to be able to have access to offfers via post types though in the future... wish the transition was smoother. |
Ok good, glad to hear the store is back up and running for now. What version of the plugin do you have running / working currently? |
I reverted to the older version and it did not make a difference. It is still telling me that my API is invalid. |
We had problems with the latest plugin that is available, and we have success with Version 3.3.3.3. |
I installed 3.3.3.3 and it "works" more than any other version has, but I am getting "Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /www/thebellwethersyndicate.com/web/wp-includes/post.php on line 2996" at the top of the page. |
The Topspin-Plugin on my Wordpress site isn't working. The API-user and API-key information is correct. It first says: "Your offers are currently being updated via the API. Your Topspin store has been successfully migrated to the new version! Please allow 15-30 minutes for the plugin to pull in new data." After refreshing I get: "Your API credentials are invalid." I have Topspin Store Plugin 4.0 Version 4.0.9.1 and Wordpress 3.5.1. This seems to have started after I updated the Graphene theme to the current version. I would refer back to past questions pertaining to the same issue, but there are no hard answers to fix the problem. Anyone...anyone...? Bueller....Bueller?
The text was updated successfully, but these errors were encountered: