Admin Styles Loading on Frontend

  • Resolved Greg Mount

    (@gregmount)


    1 week ago

    The plugin loads its editor stylesheet (handle: timeline-block-common-editor-css) on the frontend in WP v7.0.2. That handle depends on wp-edit-blocks, so WordPress also pulls in wp-reset-editor-styles, common, forms, wp-components, etc. on every public page. The result is that wp-admin/css/common.min.css gets applied to the frontend, which breaks themes badly.

    For example, its .wrap margin rule hits themes that use .wrap on the main element, and its “p { font-size: 13px }” rule overrides the theme’s body typography site-wide.

    To reproduce: activate the plugin on any site, view a frontend page logged out, and check the head for common-css and forms-css link tags.

    The editor stylesheet should be registered as editorStyle in block.json (or enqueued on enqueue_block_editor_assets) so it only loads in the editor. For now I’m dequeuing timeline-block-common-editor-css from my theme as a workaround, but this needs a fix in the plugin.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Khushwant Singh

    (@khushwantsidhu)

    6 days, 13 hours ago

    Hi @gregmount

    Thanks for spotting this issue and reporting it so clearly.
    This bug was introduced in our latest update. We are working on a fix and expect to release a bug fix update within the next 24–48 hours.

    Thanks for bringing this to our attention.

    Plugin Support Jyoti Bhandari

    (@jyoti197)

    5 days, 8 hours ago

    Hi @gregmount,

    Thank you again for reporting this issue and for taking the time to investigate it so thoroughly.

    As mentioned in our previous reply, this bug was introduced in our latest update. We’ve now resolved the issue where the editor stylesheet (timeline-block-common-editor-css) was being loaded on the frontend, causing WordPress editor styles such as common.min.css and forms.min.css to affect active themes.

    With this fix, editor-specific styles are now loaded only within the block editor and are no longer enqueued on the frontend.

    We’ve released this fix in version 1.8.3. Please update to the latest version and let us know if the issue is resolved or if you’re still experiencing any problems.

    We truly appreciate your patience, the workaround you shared, and for bringing this issue to our attention. Thank you again for helping us improve the plugin.

    Thank you

    R

    (@robinsonritch)

    5 days, 8 hours ago

    Hi, I came here to report the same issue – as not sure why but version 1.8.3 hasn’t pushed through to auto updates but will download from here to update.

    Thanks

    Plugin Support Jyoti Bhandari

    (@jyoti197)

    5 days, 7 hours ago

    Hi @robinsonritch ,

    WordPress now staggers plugin update rollouts by up to 24 hours as part of its security measures. This applies to all plugins hosted in the WordPress.org plugin directory, so the latest version may not appear in your WP Admin immediately after it has been released.

    The update should become available within the next 24 hours. If you need it right away, you can download the latest version using the link below and install it manually.

    Once you’ve updated, please let me know if the issue has been resolved. If it still persists, I’ll investigate it further and take the necessary steps to resolve it.

    Best Regards

    Thread Starter Greg Mount

    (@gregmount)

    5 days, 7 hours ago

    Version 1.8.3 installed, issue confirmed resolved.

    Thanks for the quick fix!

    Plugin Support Jyoti Bhandari

    (@jyoti197)

    5 days, 7 hours ago

    Great to hear that the issue has been resolved in version 1.8.3. Thank you for confirming!
    If our support has been helpful, we’d really appreciate it if you could take a moment to share your experience by leaving us a review https://wordpress.org/support/plugin/timeline-block/reviews/#new-post. Your feedback means a lot and helps us improve.

    R

    (@robinsonritch)

    5 days, 3 hours ago

    Thank you, @jyoti197
    Yes, issue resolved with the update.
    Thanks

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

You must be logged in to reply to this topic.