Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Zachary Brown

    (@thelastcicada)

    Ahhhh – thanks for the reply, that totally makes sense. I am very familiar with the WordPress VIP review time.

    The temporary fix looks to be working fine. Just wanted to drop in here and make sure everyone was still aware that there’s folks out here still looking forward to a new version!

    Thanks,

    Zach

    Thread Starter Zachary Brown

    (@thelastcicada)

    Hi folks,

    3 months ago, version 2.4.1 was an imminent release with a fix for this issue, but today 2.3.7 is still the version available on www.remarpro.com. As I’m using this on a fairly high profiles site and this bug has sat unresolved for months now (at least in the released version), this concerns me about the quality of this plugin and the timeliness of critical updates going forward.

    Thanks,

    Zach

    Thread Starter Zachary Brown

    (@thelastcicada)

    Thanks – I appreciate your attention to this issue. GrabPress is installed on a high traffic site with a couple of million pageviews per month and many authors, which may explain why I’m having this message triggered more often than other users. It is indeed writing to the error log and I do have logs rotating, but as it gets triggered so often, the log files balloon in size and make it difficult to find actual errors in between all the GrabPress messages. Anyways – it sounds like we are on the same page and I’m looking forward to the improvements in the upcoming release. Let me know if there’s any further information I could provide.

    Thanks!

    Zach

    Thread Starter Zachary Brown

    (@thelastcicada)

    Yep, still having the same issue. We use Jetpack and this Grabpress plugin pretty extensively and have both configured how we need for them to work how we want, so I haven’t made changes to any of the settings to see if that helps.

    Thread Starter Zachary Brown

    (@thelastcicada)

    Haven’t seen anything in the logs about the JSON API from Jetpack, so not sure that is related to this other error message we are getting. I’m a bit removed from the content creation process for this website, so not sure if we’re getting the blank posts, but I assume I’d have heard about it if we were.

    We upgraded to WordPress 3.9 today – same problem with the error messages in the logs, made no difference.

Viewing 5 replies - 1 through 5 (of 5 total)