Expired content locks keep showing even after stealing lock

[tristan]

On a fresh 2.1 install a content lock on a page expired 17 hours ago. When I edit by clicking the "Steal this lock and edit this page" functionality, add some content and submit. The content is successfully updated but the "!" icon notifying that the page is being edited by another user doesn't disappear for some reason.

[LB Back]

It seems to be a bug. If you change the "Locking Expiration Time-out (minutes):" to 0 (zero), it won't happen again on new pages. Perhaps you could copy the pages where that happens and delete the old ones to get rid of it. I just deleted all pages where it happened and then made new pages.

[tristan]

Thanks for confirming, seems a bit of a hassle to remove the pages and make new ones. If only CMS Made Simple had an export/import functionality for content pages....

[LB Back]

Well i had only 3 empty testpages sofar Did you change the "Locking Expiration Time-out (minutes):" to 0 (zero) and after that try copying them and see if the steal lock button disappears?

[tristan]

Wait a minute, you can't copy or delete locked pages. How did you remove these locked pages in the first place?

[mlestat1131]

You could also go into PHPMyAdmin and change the Sql table

[tristan]

Yeah I know, but that isn't very "simple" for regular users of course.

Opened a bug report here: http://dev.cmsmadesimple.org/bug/view/10776 by the way.

[LB Back]

Yes i deleted them in the DB.

[tristan]

@LB Back thanks! Maybe you could add your system information to my bug report by the way. Just noticed Robert replied there about how he can't reproduce this bug. The more information he has the better I suppose?

Why was this topic moved to The Lounge by the way?

[LB Back]

Added some info to the Forge. I also don't get why this post was moved to the Lounge, feels kinda hidden.

[tristan]

Thanks! Maybe the locking should be disabled by default on upgrades/new installs since people keep having problems with it?

[LB Back]

Well now we know, so it doesn't bother me anymore. Still haven't figured out what would be a scenario to use it though, but i'm sure there is.

[tristan]

Just tested on a pre release of 2.1.1 exact same problem is still present unfortunately.

To make sure I also tested with a lock on a template, these are the two locks:

(11, 'content', 1, 1, 1449853237, 1449853237, 60, 1449856837),
(13, 'template', 10, 1, 1449856954, 1449856954, 60, 1449860554);

When trying to steal the lock from that template (id 13) everything works as advertised and the lock disappears after submitting the template. When trying to steal the content lock (id 11) the CMS keeps the page in a locked state. Strangely enough content can be edited, page can be moved around, design and template can be changed, no problem at all.

Code: Select all

----------------------------------------------
Cms Version: 2.1.1
Installed Modules:
AdminSearch: 1.0
CMSContentManager: 1.0.3
DesignManager: 1.1.1
FileManager: 1.5.2
MicroTiny: 2.0.2
ModuleManager: 2.0.1
Navigator: 1.0.1
News: 2.50.3
Search: 1.50.2

Config Information:
php_memory_limit:
max_upload_size: 32000000
url_rewriting: none
page_extension:
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: UTC
permissive_smarty: false

Php Information:
phpversion: 5.6.16
md5_function: On (True)
json_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 2048
E_DEPRECATED: 0
test_file_timedifference: No time difference found
test_db_timedifference: No time difference found
create_dir_and_file: 1
memory_limit: 256M
max_execution_time: 60
register_globals: Off (False)
output_buffering: 4096
disable_functions:
open_basedir:
test_remote_url: Success
file_uploads: On (True)
post_max_size: 16M
upload_max_filesize: 32M
session_save_path: /tmp (1777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)
check_ini_set: On (True)
curl: On

Performance Information:
allow_browser_cache: Off (False)
browser_cache_expiry: 60
php_opcache: Off (False)
smarty_cache: Off (False)
smarty_compilecheck: Off (False)
smarty_cache_udt: Off (False)
auto_clear_cache_age: On (True)
Server Information:
Server Software: Apache/2
Server Api: apache2handler
Server Os: Linux 2.6.32-5-amd64 On x86_64
Server Db Type: MySQL (mysqli)
Server Db Version: 5.5.9
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable

Permission Information:
tmp: /home/test/public_html/test/tmp (0755)
tmp_cache: /test/public_html/test/tmp/cache (0755)
templates_c: /home/test/public_html/test/tmp/templates_c (0755)
modules: /home/testl/public_html/test/modules (0755)
uploads: /home/test/public_html/test/uploads (0755)
File Creation Mask (umask): /home/test/public_html/test/tmp/cache (0755)
config_file: 0444
----------------------------------------------

[calguy1000]

works fine for me, and others have tested it as well.
so, I am leaning towards it being a browser or browser plugin issue.

[tristan]

works fine for me, and others have tested it as well.

You also wrote that in the bug report, it doesn't work fine for me unfortunately. But please let me know if you want me to stop reporting about this specific bug.

Tested here with:

Browser: Safari 9.0.1
Plugins: AdobeAAMDetect

Browser: Chrome 47.0.2526.80 (64-bit)
Plugins: Widevine Content Decryption Module - Version: 1.4.8.824, Chrome PDF Viewer (2 files), Native Client, Adobe Flash Player - Version: 20.0.0.228

Browser: Firefox 42.0
Plugins: OpenH264 Video Codec provided by Cisco Systems, Inc., H264 IPC web plugin, AdobeAAMDetect, Default Browser Helper