pyxis630

Thanks. That would be great.

For me an on/off switch would be enough, other folks may have a different opinion. I assume I could then add my own scroll code in the template file, if needed.

I have to agree. The functionality seems great, but the rest leaves much to be desired.

It would probably be best if you talk to the support team of your hosting company. They probably know about this WP bug and they should know what to do.

This seems to be a nasty bug in the latest version (4.4.1) of WP. Many WP sites have been affected. Has to do with mod_security.

Hi Daniel. The server load settings, plus a the timeout setting will only work for the tar ball creation, but not for the archiving part itself.

I had too set the time out to something very low (9s) and the server load reduction to maximum. That allows the creation of the complete tar ball. There needs to be something that slows down the compression piece as well.

The support guy mentioned pigz.
What about this: https://www.php.net/manual/en/function.proc-nice.php
Could that be an option?

This could be an extra feature in your paid version if you don’t want to add something like this to the free plugin.

Thanks,
Sabine

I noticed the same issue on my blog. No page specific titles, just the generic site title and description. Existing meta data will be removed after the a post has updated via quick edit for example. It used to work just fine.

Not working for me either. Username/password are just alphanumeric, installation of the non gravity plugin doesn’t fix it either (like outlined above), although this plugin can authenticate just fine on its own. I used it before on a different site where it did work.

Don’t minify CSS and JavaScript. I found it causes more trouble than it’s worth. Most JS libraries come in a minified version, better to use those. It’s also better if you tighten up the CSS files yourself. Once you make this change and turn off the JS and CSS minify option your website should look nice again. Don’t forget to empty your cache.

I ended up starting over. Resetting the plugin, creating a new app over at twitter and made sure that I created the access token after I changed the setting to read/write. I cannot remember if I did this before, I might have created the access tokens in read only mode first and changed it afterwards and re-created them.

Although I still get the credentials missing notification, it also says it is connected and started to post to twitter. I received no errors today after posting to twitter.

Cheers,
Sabine

Just installed the plugin and get a similar message.

The credentials are correct, Twitter is set to Read and Write, I also tried with Read, Write and Access direct messages. Posting to Twitter does not work. WP to Twitter version is 2.4.4

One guy over at Twitter suggests that the plugin wasn’t authorized by Twitter (https://dev.twitter.com/discussions/3929). Could that be an option?

Thanks.