wireframed
Forum Replies Created
-
Forum: Plugins
In reply to: [User Access Manager] users getting 404 ErrorSame issue here. It’s a bit annoying, since a 404 isn’t very helpful for the user. :-/
We’ve had the problem for a while, but haven’t had time to redesign the solution.Forum: Plugins
In reply to: [mqTranslate] Long-term support of mqTranslateJust wanted to pop in and say thanks – the continuation of the qTranslate codebase is very much appreciated. qTranslate has always been one of the easier translation plugins to manage, as it didn’t create a lot of extraneous pages in the page hiearcy (which is already cluttered enough with WP’s flat structure).
If you have a paypal link or similar, I’m sure I’m not the only one who would donate a little, just to keep development going. (Even without expectation of any support – just that you guys are doing an honest effort to keep current with WP versions is enough for me).
Regards
wireframedForum: Plugins
In reply to: [Advanced AJAX Page Loader] Update body classesFor some reason I didn’t get nofitications about updates here until now. :-/
okay wrecknoble please can I have a link to your site and steps to reproduce, wireframed I think your issue is different from wrecknoble. Basically its the feature of AJAX that things will not be changed even if they changed previously, nor will any javascript events be fired which is why there is such things as reload codes.
However, if you set AAPL to reload on the <HTML> tag it might just update the classes you require, please try it.
Otherwise a reload code will need to be created for your specific requirements, this isnt something to *fix* as it is not a bug and is unavoidable.It’s not that I don’t understand the issue. 🙂 However, reloading everything in <html> kinda defeats the point of using AJAX, since you’re essentially reloading the entire page anyway. A more elegant solution would be using Javascript to inject updated <body> classes dynamically when you’re grabbing the content anyway. Particularly since WP trains you to use the <body> classes for at lot of stuff.
It’s not an insurmountable problem, but it DOES limit the plugin, which is otherwise very nice.
Regards,
Forum: Plugins
In reply to: [Advanced AJAX Page Loader] CSS gets messed up after Ajax page loadThe reason this happens is most likely that the classes WordPress puts on the body tag aren’t refreshed. Since the
<body>is outside the ID the plugin is refreshing with AJAX, it only gets updated when you force an update (which reloads the entire HTML from the server).I had the same issue with a WooCommerce shop I’m building, and am hoping that maybe the plugin author has/creates a solution.
Getting the body classes updated is kinda important for a lot of themes, since it enables you to do better CSS.A possible workaround could be to place the PHP tag that fetches the classes on an element inside the #content (or whatever ID you use for the AJAX update), but it’s a bit hacky, and won’t work if you need to use the classes for something outside that ID…