Hello
Here is a patch that preserves the content_lock_token query string parameter between form posts in order to support content_lock module.

Without the patch, content_lock refuses to create a lock, so that can prevent a CSRF attack. As a result user is been asked to manually lock the node.

By the way, I am not sure if save_edit should preserve all Request variables and not only the “destination”

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ericpinxteren’s picture

FileSize
1.5 KB

Fix path of patch.
Apply coding standard.

ericpinxteren’s picture

FileSize
1.49 KB

Fix url query.

ericpinxteren’s picture

Status: Active » Needs review
melvinlouwerse’s picture

FileSize
1.75 KB

This patch is an extention of the previous patch.

It adds:
* check if the content lock module is enabled (if not we dont need to add the token)
* When no token is present create a new one so a new node will also be locked. (previously only updates on an existing node would get a lock)

mroest’s picture

patch from @melvinlouwerse works for me!

stefanos.petrakis@gmail.com’s picture

Status: Needs review » Reviewed & tested by the community

Same here, this works for me too.
I will set this to "RTBC".

NitinSP’s picture

Assigned: Unassigned » NitinSP
NitinSP’s picture

Status: Reviewed & tested by the community » Fixed
NitinSP’s picture

Assigned: NitinSP » Unassigned
Status: Fixed » Reviewed & tested by the community
stefanos.petrakis@gmail.com’s picture

Status: Reviewed & tested by the community » Needs review
FileSize
1.72 KB

Rerolled against latest dev