WordPress.com edit post redirects

Redirects the new post page to the classic post page

You will need to install an extension such as Tampermonkey, Greasemonkey or Violentmonkey to install this script.

You will need to install an extension such as Tampermonkey to install this script.

You will need to install an extension such as Tampermonkey or Violentmonkey to install this script.

You will need to install an extension such as Tampermonkey or Userscripts to install this script.

You will need to install an extension such as Tampermonkey to install this script.

You will need to install a user script manager extension to install this script.

(I already have a user script manager, let me install it!)

You will need to install an extension such as Stylus to install this style.

You will need to install an extension such as Stylus to install this style.

ستحتاج إلى تثبيت إضافة مثل Stylus لتثبيت هذا النمط.

ستحتاج إلى تثبيت إضافة لإدارة أنماط المستخدم لتتمكن من تثبيت هذا النمط.

ستحتاج إلى تثبيت إضافة لإدارة أنماط المستخدم لتثبيت هذا النمط.

ستحتاج إلى تثبيت إضافة لإدارة أنماط المستخدم لتثبيت هذا النمط.

(لدي بالفعل مثبت أنماط للمستخدم، دعني أقم بتثبيته!)

المؤلف
tPenguinLTG
التثبيت اليومي
0
إجمالي التثبيت
189
التقييمات
2 0 0
الإصدار
1.6.0
تم إنشاؤه
13-03-2015
تم تحديثه
03-10-2020
الحجم
4.57 KB
الترخيص
MPLv2.0
ينطبق على

wpcom-edit-post-redirect.user.js

WordPress.com has removed the preference to edit posts using the classic interface. This user script forces a redirect to the classic interface when the new edit interface is visited.

Installation

If you don't already have one, install a browser extension that allows you to run user scripts. Then, visit the URL below:

https://github.com/tpenguinltg/wpcom-edit-post-redirect.user.js/raw/master/wpcom-edit-post-redirect.user.js

Also on Greasy Fork.

Known Issues

  • The new interface will sometimes start loading and appear before the redirect occurs
  • The redirection will likely fail on Jetpack-enabled sites whose site root is different from its installation root (e.g. the site is accessed from http://example.com/, but the installation root is http://example.com/wordpress/).

Other workarounds

If you don't like this script or can't use it for any reason, there are other workarounds available.

Changelog

  • v1.6.0: Update for new block editor redirect on old classic editor URLs. Also clean up code.
  • v1.5.0: Update for a slight restructuring in the editor page. This only affects the fallback attempt.
  • v1.4.0: Update for new editor
  • v1.3.1: Fix new post redirection for default blog
  • v1.3.0: Fix new post redirection for private and Jetpack-enabled blogs
  • v1.2.3: Code cleanup and documentation
  • v1.2.2: Fixed redirection for private and Jetpack-enabled blogs
  • v1.2.1: Remove testing code that prevented redirection
  • v1.2.0: Add redirect for unattached post editing
  • v1.1.0: Add support for editing pages
  • v1.0.2: Reduce to single regex call
  • v1.0.1: Change updateURL to point to GitHub source
  • v1.0.0: Initial release