The Ultimate Patch to 1.0

After reviewing some of the issues, mainly

• #1650012: More attributes, correct class attribute usage, and real views token support
• #1928746: add an option to add text on link as a HTML text
• #2119615: Allow replacement tokens from the first row like global text area
• #1722258: add an option to add the current page as a query destination

I feel I wanted to bring all these together and add a few more things to the mix.

First of all, the default limit of 64 characters on the querystring has meant that one could easily run that field out with a fairly complex and long querystring, so I've increased it to 2048. Doesn't mean you should use it all. Some browsers won't like it. But at least it's there to work with.

Furthermore, if anyone tried to work with Tokens and the Prepopulate module, you know the feeling of having your URL not work and things just end up being basically Global: Custom Text. Well, this patch to 7.x-1.0 of the module attempts to rectify this.

I ran into the need to use { } curly braces for this. Check out the option "Use curly brackets in tokens." to understand what I mean. By having the choice to have tokens for this Global Link field be square brackets or curly brackets means you can have some pretty awesome querystrings.

?uuid=e6305d24-5d22-43d1-a5db-f61aafcce519&changed=%5Bedit_link%5D&field_source=542&destination=node/542/display

In the result above, the querystring in the Global Link settings looks like this:

uuid={uuid}&changed=[edit_link]&field_source=!1

Along with the "Set destination as the current page" option checked.

Hope this helps everyone.