Title: Permalink skips posts
Last modified: September 27, 2024

---

# Permalink skips posts

 *  Resolved [thebigbanik](https://wordpress.org/support/users/thebigbanik/)
 * (@thebigbanik)
 * [1 year, 8 months ago](https://wordpress.org/support/topic/permalink-skips-posts/)
 * Hi, I am trying your plugin (lite version) to autogenerate the permastructures
   of posts under CPTs. I have already set how exactly I need the structure after
   the post title (-%hour%%post_id%) and I am dealing with this. Created 4 posts
   almost immediately (1-2 seconds time difference) and the custom permalinks applied
   to half of them in the order: 1st post (worked), 2nd post (not worked), 3rd post(
   worked), 4th post (not worked). it looks like the process skips one post each
   time. Is this a known behavior? Should this work like that? Is there a setting
   that I have to take under consideration? Thanks.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fpermalink-skips-posts%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Author [Maciej Bis](https://wordpress.org/support/users/mbis/)
 * (@mbis)
 * [1 year, 8 months ago](https://wordpress.org/support/topic/permalink-skips-posts/#post-18041598)
 * Hi [@thebigbanik](https://wordpress.org/support/users/thebigbanik/),
 * I apologize for the inconvenience. To be honest, I have never tested the plugin
   in such scenario, but I guess that the problem here is that all the custom permalinks
   are stored serialized in _$permalink\_manager\_uris_ global. I am not exactly
   certain how exactly you add the new posts, but apparently the _update\_option()_
   function that saves custom permalink behaves like it is called asynchronously.
 * Theoretically, if you create a first post, Permalink Manager will append the 
   new permalink to the end of custom permalinks array inside the global variable
   and finally save the whole _$permalink\_manager\_uris_ in the database. The problem
   may appear, if you publish another post before the _$permalink\_manager\_uris_
   global with the custom permalink for first post is saved to the database. Then,
   the array with custom permalink for earlier post can be overwritten with the 
   array including the newer post’s but without the custom permalink for earlier
   post.
    -  This reply was modified 1 year, 8 months ago by [Maciej Bis](https://wordpress.org/support/users/mbis/).
 *  Thread Starter [thebigbanik](https://wordpress.org/support/users/thebigbanik/)
 * (@thebigbanik)
 * [1 year, 8 months ago](https://wordpress.org/support/topic/permalink-skips-posts/#post-18044711)
 * Hi, thank you for the reply. I use Jet Forms to create the posts form the front
   end. I was testing this scenario in case multiple users create a new post at 
   the same time. Jet forms use the Insert Post instead of Update post, so maybe
   this is the reason or maybe as you said this small time difference until data
   is saved in database, I any case, I have to keep that in my mind and check the
   new post’s url often and regenerate manually.

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

The topic ‘Permalink skips posts’ is closed to new replies.

 * ![](https://ps.w.org/permalink-manager/assets/icon.svg?rev=2625166)
 * [Permalink Manager Lite](https://wordpress.org/plugins/permalink-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/permalink-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/permalink-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/permalink-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/permalink-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/permalink-manager/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [thebigbanik](https://wordpress.org/support/users/thebigbanik/)
 * Last activity: [1 year, 8 months ago](https://wordpress.org/support/topic/permalink-skips-posts/#post-18044711)
 * Status: resolved