[wp-trac] [WordPress Trac] #65189: create pattern issue

[WordPress Trac]

#65189: create pattern issue
-----------------------------+-------------------------------
 Reporter:  sonaliprajapati  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  coding-standards
-----------------------------+-------------------------------

Comment (by darshitrajyaguru97):

 I tested this issue further directly on the WordPress.org Pattern Creator
 and was able to consistently reproduce it.

 == Testing Performed ==

 * Opened the WordPress.org Pattern Creator
 * Created a new pattern with all required information
 * Submitted the pattern normally

 == Observed Behavior ==

 * After submission, a “Thank you for submit” message appears briefly
 * A few seconds later, the editor shows an error state, and the pattern is
 not created successfully
 "There is an issue with your pattern.
 Updating failed. Sorry, you are not allowed to edit the
 jetpack_post_was_ever_published custom field."

 == Console / Network Findings ==

 On further inspection in the browser console and network tab, several REST
 /API-related issues appeared during the submission process.

 Most relevant finding:

 {{{
 POST https://wordpress.org/patterns/wp-json/wp/v2/users/me?_locale=user
 404 (Not Found)
 }}}

 Additionally:

 {{{
 wp-json/wp/v2/media?... 403 (Forbidden)
 wp-json/wp/v2/wporg-pattern/{id}?_locale=user 403 (Forbidden)
 }}}

 There are also multiple async/runtime listener errors and failed resource
 requests occurring after submission.

 == Notes ==

 * Issue tested directly on WordPress.org Pattern Creator (not local
 environment)
 * Reproducible consistently
 * Tested in Chrome on Windows
 * The pattern submission initially appears successful before failing
 during subsequent API/editor requests

 Based on the testing, this may be related to:

 * REST API routing
 * Authentication/nonce handling
 * Permission validation
 * Post-submit editor requests on WordPress.org infrastructure

 The `users/me` request returning `404` and related `403` API responses may
 help identify the root cause.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65189#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform