COMPLAINT

• 

  mohammedlefta · Member · Jun 14, 2025 at 2:33 pm

  • Copy link
  • Add topic to favorites

  Urgent: Critical Site Editor Bug Preventing Basic Site Management on Free WordPress.com Plan
  Hello WordPress.com Community and Staff,

  I am writing to escalate a severe and persistent bug I am experiencing with my free WordPress.com site (dubsikcom.wordpress.com). This issue is preventing me from performing basic site management tasks, specifically managing my navigation menu, and all troubleshooting has failed.

  The core problem is that my Site Editor (Appearance → Editor) is fundamentally broken and unusable.

  Site Details:
  Platform: Free WordPress.com plan.

  Theme: Block theme (Twenty Twenty-Three / Twenty Twenty-Five).

  Goal: Add categories to my navigation menu.

  The Problem – A Severely Broken and Intermittent Site Editor:
  When I access the Site Editor, it primarily displays ‘NO BLOCKS AT ALL.’ This is not a matter of misplacement; the editor content area itself is empty, and I cannot select any blocks (including the Navigation block). The List View sidebar also consistently shows as empty.

  Crucially, this is an intermittent rendering issue. At one point, the List View briefly showed a ‘Paragraph’ block, and parts of my site’s content (like ‘About,’ ‘Privacy,’ ‘Social’ links) briefly appeared in the editor, only to vanish again, returning to a completely empty state. This makes the editor impossible to use for any design or content management.

  Technical Evidence of a Platform-Level Bug:
  This is not a user-error or a simple setting issue. There is strong evidence pointing to a problem on the WordPress.com platform’s side:

  Jetpack Console Errors:
  When checking my browser’s developer console in the Site Editor, I consistently find the following critical red JavaScript errors:

  Store ‘jetpack-modules’ is already registered.

  Store ‘jetpack-ai/logo-generator’ is already registered.

  Jetpack Connection package: Initial state is missing. Check documentation to see how to use the Connection composer package to set up the initial state.
  These errors strongly indicate a core issue with Jetpack’s integration or initialization on my site, which is likely causing the editor’s malfunction.

  Inability to Access WP Admin:
  I have repeatedly attempted to access the traditional WP Admin dashboard, as suggested by support, but have been completely unsuccessful by all methods:

  The ‘WP Admin’ link is not visible in the ‘Quick Links’ section or anywhere else in my main WordPress.com dashboard.

  Direct URLs (dubsikcom.wordpress.com/wp-admin and https://wordpress.com/wp-admin/dubsikcom.wordpress.com) consistently result in a ‘Page did not exist’ error or do not load, even when I am logged in.

  Exhaustive Troubleshooting (All Failed):
  I have meticulously followed every single troubleshooting step suggested by the WordPress.com support system, with consistent failure to resolve the issue:

  Browser-Level:

  Cleared browser cache and cookies.

  Cleared specific WordPress.com cookies.

  Tried using incognito mode.

  Tested in different web browsers (Chrome, etc.).

  Performed hard refresh (Ctrl+Shift+R / Cmd+Shift+R).

  Result: NO CHANGE to the empty Site Editor.

  Editor-Level:

  Attempted to reset templates (while the ‘Templates’ list became visible, this did not resolve the empty List View or block rendering).

  Temporarily switched to a different WordPress.com block theme (e.g., Twenty Twenty-One / Twenty Twenty-Two).

  Result: NO CHANGE. The List View remained empty, confirming the issue is NOT theme-specific.

  Block-Level (Suggested by Support, but Impossible to Try):

  Suggestions to use the six dots handle, up/down arrows, parent selector, or breadcrumbs to move/select blocks cannot be performed because the editor shows ‘NO BLOCKS AT ALL’ in the first place.

  Suggestions to ‘Attempt Block Recovery’ or check for ‘Unexpected or invalid content’ errors within the editor also yield no results because no blocks are rendered for these options to appear.

  Suggestions to install plugins (e.g., Health Check & Troubleshooting) are impossible on a free WordPress.com plan.

  The Support Experience & Need for Direct Intervention:
  I have engaged extensively with the WordPress.com support system. While I appreciate their initial attempts to provide troubleshooting steps, the process has reached an impassable point.

  Crucially, the support system itself identified this as a ‘Jetpack connection issue’ and a ‘platform-level issue.’ Despite this diagnosis of a core system bug, when I requested to be connected with a human support agent for direct investigation (as they had offered), I was refused unless I upgraded to a paid plan.

  This situation is unacceptable. I am unable to use the core features of my free WordPress.com site due to a fundamental bug on your platform’s end, confirmed by technical errors, and I am being denied direct assistance unless I pay.

  Call to Action:
  I urgently request that WordPress.com staff:

  Acknowledge and investigate this severe, persistent, and intermittent rendering bug directly on my account.

  Provide a solution to restore full functionality to my Site Editor, including the List View and proper block rendering, so I can manage my website.

  This issue is beyond any user-level troubleshooting. Your direct intervention is required.

  Thank you for your prompt attention to this matter.

  Sincerely,

  A Frustrated WordPress.com User
  (MOHAMMED LEFTA )

  WP.com: Yes
  Jetpack: No
  Correct account: Yes

  The blog I need help with is: (visible only to moderators and staff)

• 

  mohammedlefta · Member · Jun 17, 2025 at 10:45 am

  • Copy link

  I THINK I HAVE WAITED LONG ENOUGH FOR CLARIFICATION FROM YOUR SIDE ABOUT THE COMPLAINTS I POSTED ABOVE. THIS PROVES ONE THING TO ME: YOU INTENTIALLY PUT THOSE HURDLES TO PUSH PEOPLE LIKE ME TO UPGRADE AND THE FREE PLAN THEMES IS ONLY A JOKE . HERE IS A SUMMARY OF WHAT I HAVE FACING …”

  This outlines the key challenges encountered while attempting to set up a basic blog using a free plan and modern block theme on WordPress.com:

  1. Non-intuitive Interface for Basic Customization: The shift from traditional WordPress “Widgets” to the “Full Site Editing” (FSE) experience within the “Appearance > Editor” proved significantly more complex for fundamental layout adjustments, such as managing sidebar content.
  2. Difficulty Removing Default/Duplicate Content: Removing automatically generated or duplicated elements in the sidebar (e.g., redundant “About” links, “Recent Posts,” “Author Biography”) was a struggle, as these could only be managed within the less intuitive Site Editor using block manipulation, rather than a clear widget interface.
  3. Persistent Failure to Add Navigation Links: The most significant hurdle was the repeated inability to add a crucial “About” page link to the main navigation menu. Despite the page being published and attempting to add its correct public URL (and even a simple test URL like https://example.com), the system consistently returned “No results found” or failed to register the link. This behavior made a basic site navigation impossible to configure through standard means.
  4. Confusion Between Public and Admin URLs: The distinction between public-facing page URLs and internal administrative editing URLs added an unnecessary layer of complexity when trying to link content, as the editor did not provide clear feedback for incorrect URL types.

  These challenges effectively presented significant “hurdles” to a user attempting to establish a functional, simple blog on the free plan, creating an impression that basic customization is intentionally made difficult, potentially to encourage an upgrade.