Multiple instances need to be applied to different elements in the DOM
otherwise multiple menus will be called for each click/right click.
e.g.
jQuery(document).ContextMenu(url);
would work for any form on a page. Using this would mean that multiple
instances couldn't be used though
jQuery('#content form').eq(0).ContextMenu(url);
jQuery('#content form').eq(3).ContextMenu(url);
Using the above 2 menus will be created for the first and 4th forms on
the page. Any of forms won't response to menu clicks.
jQuery(docuemnt).ContextMenu(url);
jQuery('#content form').eq(0).ContextMenu(url);
With the above any form on the page will respond to menu clicks but the
first form will send 2 requests for the context menu.
The ajaxStart/ajaxStop functions were being called before the document
was ready and the 'ajax-indicator' element existed. This meant that they
would never be called when an ajax event happened.
Textile doesn't "understand" :only_path => false and thus doesn't convert links of the form
<pre>"foo":/bar</pre>
to full URLs, this is done in a subsequent method akin to the wiki_lins and so on
Since Rails 2.3.11, protect_from_forgery exclusively calls
handle_unverified_request which defaults to resetting the session. The old
code to handle an invalid CSRF token is not used anymore and is thus
removed to un-confuse people.
pg was locked to ~> 0.9.0 as it was the last version to support ruby 1.8.6, we don't support it officially anymore, thus we can remove the version requirement.
Contributed by Dies Koper.
This will prevent the usage of the wrong wiki_content status.
The code is not overly pretty and deserves a thorough refactoring, but at
least it solves the problem at hand.
It completely breaks on Ruby 1.9.3-p0. This is a stopper for people installing all groups. For the rest it is rarely used at all. Developers and testers requiring it can include it into their Gemfile.local
This will prevent the usage of the wrong wiki_content status.
The code is not overly pretty and deserves a thorough refactoring, but at
least it solves the problem at hand.
It completely breaks on Ruby 1.9.3-p0. This is a stopper for people installing all groups. For the rest it is rarely used at all. Developers and testers requiring it can include it into their Gemfile.local
Andrew Smith
Andrew Smith
Gregor Schmidt
Felix Schäfer
Holger Just
Michaël Rigart
Holger Just
Eric Davis
Dominique Feyer