# Bug in Wordpress plugin: quick edit forces old topics to be pushed

**URL:** https://meta.discourse.org/t/bug-in-wordpress-plugin-quick-edit-forces-old-topics-to-be-pushed/336882
**Category:** WordPress
**Tags:** wordpress, wp-discourse
**Created:** [November 19, 2024, 6:10am UTC](https://meta.discourse.org/t/bug-in-wordpress-plugin-quick-edit-forces-old-topics-to-be-pushed/336882 "2024-11-19T06:10:56Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![SkyeDragon](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@SkyeDragon](https://meta.discourse.org/u/SkyeDragon)
#### Post date: [November 19, 2024, 6:10am UTC](https://meta.discourse.org/t/bug-in-wordpress-plugin-quick-edit-forces-old-topics-to-be-pushed/336882/1 "2024-11-19T06:10:56Z")

</div>

The wordpress plugin is great, I love being able to link my blog and forum!

But, I have noticed a bug: the quick edit feature in the wordpress post list seems to ignore the publish settings and always publishes blog articles to forum.

I have the auto publish setting on for **new** posts to be published to Discourse. I also have ‘force publish max age’ to 3 days. Regardless of whether I have ‘force publish’ turned on or off, in either situation using the quick edit feature and changing any value (ex adding/removing tag, changing timestamp, etc) causes the (old) blog article to be published to discourse. If I do a full edit, this does not happen and it works as expected.

FYI it only happens the first time a post is quick edited, unlinking + quick edit again does not cause it to occur again.

I have ten years of blog posts (😅) so I do not want my new forum to be filled up with old posts accidentally, heh…

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [November 19, 2024, 8:16am UTC](https://meta.discourse.org/t/bug-in-wordpress-plugin-quick-edit-forces-old-topics-to-be-pushed/336882/2 "2024-11-19T08:16:27Z")

</div>

Thanks for the report, I’ll investigate and add any necessary fixes in the next version of the plugin.
