WordPress.com edit post redirects

Redirects the new post page to the classic post page

Від 14.06.2015. Дивіться остання версія.

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.

(У мене вже є менеджер скриптів, дайте мені встановити його!)

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.

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

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

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

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

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

Автор
tPenguinLTG
Рейтинги
0 0 0
Версія
1.3.1
Створено
13.03.2015
Оновлено
14.06.2015
Size
3,6 кБ
Ліцензія
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

    • For unattached post editing (i.e. editing a new post without first specifiying a blog; accessed from https://wordpress.com/post), the new editor will load completely before being redirected.
    • The new editor will also load completely for private and Jetpack-enabled. This is an API limitation.
  • When editing new posts (i.e. posts without a post ID) on Jetpack-enabled sites, the redirection will likely fail if the site root is different from the 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.0.0: Initial release
  • v1.0.1: Change updateURL to point to GitHub source
  • v1.0.2: Reduce to single regex call
  • v1.1.0: Add support for editing pages
  • v1.2.0: Add redirect for unattached post editing
  • v1.2.1: Remove testing code that prevented redirection
  • v1.2.2: Fixed redirection for private and Jetpack-enabled blogs
  • v1.2.3: Code cleanup and documentation
  • v1.3.0: Fix new post redirection for private and Jetpack-enabled blogs