chrisdwarner
Forum Replies Created
-
Jermey,
I have my blog hosted through dreamhost.com, and they as part of their wordpress support, have just upgraded everyone to jetpack premium.
Now everything is automagically working, my stats page is correctly displaying stats… I suspect that my issues were part of a side effect of them rolling out this new feature. That would explain the server 500 errors I was getting when trying to delete the plug in.
Certainly would be nice to get some forewarning from your ISP if they are going to be doing stuff like this.
anyhow, thanks for your help… I don’t know what you did (if anything on your end) but thank you for your assistance and patience while helping me with this issue.
- This reply was modified 9 years ago by chrisdwarner.
I have tried after flushing cookies, same error. Issue #6938 reproduces when I am trying to delete jetpack, and also when I try to disconnect my site from jetpack. You can add that to the bug notes.
FWIW, I can view the conedogers.com stats just fine using the wordpress mobile app. I had to reconnect the blog to re-enable the stats. Basically, everything you recommended worked on my IOS mobile device using your wordpress app.
Its only the browser where I have issues. I tried to deactivate and delete the plugin on the wpAdmin page, but I get a repeatable server 500 error when I attempt to delete the plugin. That leaves the plugin in an unknown state, the only way to continue is to re-install over the broken plugin. I was about to try deleting the plugin via FTP and try to re-install.
- This reply was modified 9 years, 1 month ago by chrisdwarner.
close… but now we are at the point where I first contacted you. I can’t see the stats for conedogers.com, instead, I see the stats for conedogers.wordpress.com
Also, it show my site redirect to conedogers.com as expired when it is valid through november of this year.
I see the redirect that I purchased, but I do not see my blog in the list of sites.
instead I see a prompt for 3 hidden blog sites. viewing those sites, I see my original wordpress.com site. only clicking on the url redirects me to the active blog as expected.
Moving on to the next step, I open the dashboard and Jetpack is asking me to activate recommended features. Clicking that button I get the following Javascript error: “Recommended features failed to activate. Error: Cookie nonce is invalid”
this is as far as I get. I get the same error when I attempt to delete the plugin, deactivate, etc..
I had no idea I had two accounts linked.. and I never attempted to add a second account 2 weeks ago. At least not deliberately. Obviously lets go with the account I used to create my original wordpress.com account.
I suspect someone tried and failed to hijack my blog…
Hi Jeremy,
the site url is http://www.conedogers.com. I have lost track of the ID of the ticket(s) that I opened.
At this stage, I have been able to restore the stats page on my mobile device by remove and re-adding the site on the wordpress app and I can see site stats as expected, so I think my problem is local to either my machine, or wordpress site.
Now, when I try to disconnect jetpack from my wordpress account, I am unable to delete jetpack with similar scripting errors. So I think my jetpack install on my site is fubar, How do I manually delete the jetpack plugin from wordpress?
Also, at some point earlier this year, wordpress started asking for local data storage according to safari. How do I delete that cache? I suspect that might be part of my jetpack problem. does jetpack use any of that local data storage?
thanks
chris
Jeremy,
I have been struggling with the same issue. I reached out to your tech support and they were A) not helpful, b) I kind of feel like they blew me off because I have not heard any response from them in over 5 days on this issue.
I have been looking around for anything recent article related to this problem when I stumbled upon this post.
I have the very same problem. It started about a month ago. When I would view my stats, I started getting Javascript errors when loading the stats page. I could never get the page to completely load properly. Then Jetpack got upgraded and all hell broke loose.
The javascript error on the stats page went away, but also my stats.. I had no stats at all.
Then I noticed that my jetpack redirect was not redirecting anymore. I have a valid redirect subscription through november of this year, and now it’s showing expired after you (wordpress) tried to run my credit card to renew the already valid redirect. The card info was expired, the charge didn’t go through, and now I have a broken redirect service. THIS IS UNRESOLVED and your tech support has totally dropped the ball on this. I am a bit angry about this…
Now I am trying to do the steps you mentioned in your reply and I can’t disconnect jetpack because of scripting errors. Now I get an error “There was an error disconnecting Jetpack. Error:Error: Cookie nonce is invalid”
So I am pretty suck, frustrated, and quite annoyed at the lack of help by your tech support.
What do I need to do to fix this problem?
Forum: Fixing WordPress
In reply to: forced upgrade to 4.1.5 caused problemsI don’t know that answer, I would suggest you contact godaddy.com support for more help.
Forum: Fixing WordPress
In reply to: forced upgrade to 4.1.5 caused problemssharadnagare,
I had to log into my wordpress hosting service and reboot my wordpress instance.
try rebooting your wordpress server, that resolved the problem for me.
Forum: Fixing WordPress
In reply to: forced upgrade to 4.1.5 caused problemsafter rebooting my wordpress server and database server, the access was restored.
Don,
found it… you should put this link in your docs, it really helped me diagnose the problem..
http://associates-amazon.s3.amazonaws.com/scratchpad/index.htmlwhen I copied by secret key I missed a couple of characters on the string.
every thing is working now, both with file_content() and CURL.
I checked the code on the HTML output and found this..
HIDDEN APIP ERROR: SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.This was after creating fresh keys on amazon
don,
that got rid of the error, but still no ad on the page.
The page is very simple, here is the complete contents.
this is a test of the amazon embedding
[AMAZONPRODUCTS asin=”B000CPAEJ0″]