Blocks that are troublesome by AJAX
Permalink Browser Info Environment
An ongoing summary of what will and won't work when used with 'Blocks by AJAX', either with specific Blocks by AJAX templates or via stacks.
See also http://www.concrete5.org/marketplace/addons/blocks-by-ajax/forums/b... for notes on blocks that are fully compatible and http://www.concrete5.org/marketplace/addons/blocks-by-ajax/forums/t... for how to quickly test if a block will be AJAX loadable.
See also http://www.concrete5.org/marketplace/addons/blocks-by-ajax/forums/b... for notes on blocks that are fully compatible and http://www.concrete5.org/marketplace/addons/blocks-by-ajax/forums/t... for how to quickly test if a block will be AJAX loadable.
| Type: | Discussion |
|---|---|
| Status: | New |
The standard Concrete5 Guestbook and Survey blocks will not work in a custom 'Blocks by AJAX' template, but do work if loaded in a stack using the Stack Randomizer 'Blocks by AJAX' template.
http://www.concrete5.org/marketplace/addons/stack-randomizer/...
This appears to be a confusion with the way the C5 dispatcher validates the token associated with block actions.
I anticipate that some other blocks that submit a form back to the block controller may have the same restrictions when used with Blocks by AJAX and will consequently need to be AJAX loaded from a stack.
http://www.concrete5.org/marketplace/addons/stack-randomizer/...
This appears to be a confusion with the way the C5 dispatcher validates the token associated with block actions.
I anticipate that some other blocks that submit a form back to the block controller may have the same restrictions when used with Blocks by AJAX and will consequently need to be AJAX loaded from a stack.
This may be solvable by changing the block controller and the script loading.