"Manage All Content" off without losing drag page reordering

[Guido]

I'm setting up an "editor" user and came across the following "bug" (as I percieve it): When I turn off "Manage All Content" for the editor-group, an editor can't re-order pages using the drag-n-drop functionality under "options". In stead, he/she has to use the blue arrows to move the page by one position. Kinda tedious when you want to re-order a page 10 places up or down. But I don't want to give editors the full monty during page editing.

So it's either giving editors freedom to mess things up, or limiting their ability to re-order pages in a quick-n-nice way. Is there any dot on the roadmap for improving this?



----------------------------------------------

Cms Version: 2.1.4

Installed Modules:

AceEditor2: 1.05
AdminSearch: 1.0.1
CGExtensions: 1.53.9
CGSimpleSmarty: 2.1
CGSmartImage: 1.21.5
CGSnapshot: 1.2
CMSContentManager: 1.1
CMSMailer: 6.2.14
CustomGS: 2.2
DesignManager: 1.1.1
ECB2: 1.1
FileManager: 1.5.2
FormBuilder: 0.8.1.4
Gallery: 2.1.6
JMFilePicker: 1.0
LISE: 1.2.1.1
LISEcars: 1.2.1.1
LISEprojecten: 1.2.1.1
MicroTiny: 2.0.3
ModuleManager: 2.0.2
Navigator: 1.0.3
News: 2.50.5
Search: 1.50.2
TinyMCE: 3.1.3


Config Information:

php_memory_limit:
max_upload_size: 64000000
url_rewriting: mod_rewrite
page_extension:
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: Europe/Amsterdam
permissive_smarty: false


Php Information:

phpversion: 5.6.26
md5_function: Aan (Waar)
json_function: Aan (Waar)
gd_version: 2
tempnam_function: Aan (Waar)
magic_quotes_runtime: Uit (Onwaar)
E_ALL: 22527
E_STRICT: 0
E_DEPRECATED: 0
test_file_timedifference: Geen tijdsverschillen gevonden
test_db_timedifference: Geen tijdsverschillen gevonden
create_dir_and_file: 1
memory_limit: 128M
max_execution_time: 30
register_globals: Uit (Onwaar)
output_buffering: 4096
disable_functions:
open_basedir: /MY_SERVER/:/tmp:/var/tmp:/usr/local/lib/php/:/usr/local/php56/lib/php/
test_remote_url: Succes
file_uploads: Aan (Waar)
post_max_size: 64M
upload_max_filesize: 64M
session_save_path: Geen controle omdat 'open_basedir' actief is
session_use_cookies: Aan (Waar)
xml_function: Aan (Waar)
xmlreader_class: Aan (Waar)
check_ini_set: Aan (Waar)
curl: Aan


Performance Information:

allow_browser_cache: Uit (Onwaar)
browser_cache_expiry: 60
php_opcache: Uit (Onwaar)
smarty_cache: Uit (Onwaar)
smarty_compilecheck: Uit (Onwaar)
smarty_cache_udt: Uit (Onwaar)
auto_clear_cache_age: Aan (Waar)

Server Information:

Server Software: Apache/2
Server Api: apache2handler
Server Os: Linux 2.6.32-642.4.2.el6.x86_64 Aan x86_64
Server Db Type: MySQL (mysqli)
Server Db Version: 5.6.33
Server Db Grants: Er is een "GRAND ALL" permissie gevonden, alles lijkt in orde.


Permission Information:

tmp: /MY_SERVER/public_html/renard/tmp (0755)
tmp_cache: /MY_SERVER/public_html/renard/tmp/cache (0755)
templates_c: /MY_SERVER/public_html/renard/tmp/templates_c (0755)
modules: /MY_SERVER/public_html/renard/modules (0755)
uploads: /MY_SERVER/public_html/renard/uploads (0755)
Bestandscreatiemasker (umask): /MY_SERVER/public_html/renard/tmp/cache (0755)
config_file: 0644

----------------------------------------------

[calguy1000]

Here's how it works.

'Manage All Content' is like the 'superuser' of content pages. With that permission, a user can do anything to any content page.

If a user only has 'Modify Any Page' permission they are treated exactly like an 'additional editor'. Just for every content page.

Owners/Additional Editors can only re-order pages using the up/down arrows because there are special rules for how pages can be re-ordered with limited permissions on only some pages.

I don't think it's a bug that some users don't have the ability to graphically re-order content (you haven't explained how you set things up), just a decision.

[Guido]

Well, I understand why there are different permission levels (and I like that). It allows me to limit the amount of 'clutter' for an editor. But I don't understand why that has to apply on the order of pages (probably something about the core I don't know).

The problem is, imagine yourself being an editor. You have a page that has 20 child pages, and you'd like to move childpage 18 to position 3. You'd need 15 clicks, waiting between every click. Maybe the filosophy is that editors shouldn't be in charge of page ordering (and designers should have that task), but really that's not the type of business I develop for. SMB (Small and Medium Businesses) often have one person maintaining the site and don't really like having to log out and back in again as a different user just to do some re-ordering.

Sure, it's not really a bug. More of a feature I think would be quite useful. So maybe I'm just whining here about something only I'd like, but maybe there are more people who'd like this feature?