OldGrumpyDE
Forum Replies Created
-
Forum: Plugins
In reply to: [Statify – Extended Evaluation] Removed from WordPress?Any update on this topic? I’d be fine with the old, removed version, it’s just for evaluation.
@mikacns the problem is that you have wrong quote marks in the lines you pasted. There should be single quotes but the paste contains ticks and backticks as quotes. You can see it in your codeshare.io-Link if you look closely at lines 104-111 (wrong quotes) as compared to line 91 and following (correct quotes).
Sometimes, Mailservers are configured to disallow mail sent locally via SMTP (for various reasons, ahem). Can you check if yourdomain.name and smtp.yourdomain.name point to the same server? If they do, it might be worth a try to set the smtp host to “localhost” or “127.0.0.1” (please test both, trust me on that one).
Forum: Plugins
In reply to: [Shariff Wrapper] jQuery collision (Type Error: $ is not a function)Jan, thanks for your valid concerns. I probably shouldn’t have posted it that way, and I second your thoughts that it’s a bad idea in general. But in this case it’s about tracking down an issue between seasoned developers in a most convenient way. Rest assured, the test system is all locked up and closely monitored. Violators will be wrist-slapped or eaten by a grue as appropriate. 😉
In other news, I fixed the problem by beating the stupid $(…) out of the code and replacing it with the correct jQuery(…) – it’s working now. If you want a detailed elaboration why you shouldn’t use the $() shortcut in WordPress plugins, here is an interesting article about it: http://devotepress.com/wordpress-coding/how-to-properly-use-jquery-scripts-in-wordpress/
The problem occurred because the shariff wrapper wasn’t the only member playing “foul” here, there are at least half a dozen instances of $() usage spread across the eco system in question. I also filed a comment for the theme developer, hope dies last, you know. 😉
Forum: Plugins
In reply to: [Shariff Wrapper] jQuery collision (Type Error: $ is not a function)Hi JP, “the plugin doesn’t include an own jQuery version” is exactly my problem. 🙂 Unfortunately, the theme I have to use comes with 5 (yes, FIVE) required plugins and I can’t switch to another theme – one of those plugins (or the theme itself, I still need to dig through it) loads jQuery improperly, making shariff fail to display at all. I can fix that by replacing the shariff minimized libs in the wrapper with the “full” shariff libs which include their own jQuery version.
However, I just noticed that clicking through still fails, doh. I can setup a test site for you if you want to have a look, just let me know where to send login credentials. I can only work at the live site during nighttime. 😉
Forum: Plugins
In reply to: [qTranslate X] qTranslate-X and Fusion Page Builder@raji Web
I hope you’re aware of the huge leak you’ve just blown into your website security.
Forum: Plugins
In reply to: [qTranslate X] qTranslate-X and Fusion Page BuilderIf anybody from the dev team would like to have a look at it now that 3.3 is out, just let me know. I’ll setup a test installation for you.
Forum: Plugins
In reply to: [qTranslate X] qTranslate-X and Fusion Page BuilderOh, sorry, this was easy to misunderstand. I meant an ETA for version 3.3 so I can jot down “don’t bother checking before x/y”. 🙂
Forum: Plugins
In reply to: [qTranslate X] qTranslate-X and Fusion Page BuilderDo you have a rough estimate for the ETA? I’m not trying to urge, I’m just asking for my own schedule.
Forum: Plugins
In reply to: [qTranslate X] qTranslate-X and Fusion Page BuilderJust re-tested with 3.2.9.9.8 and no change. Even in single-language mode, the editor displays the content for all languages and even the qtranslate-x shortcodes like [:de] etc.
When I switch back to the default editor, I see all of the shortcodes qtranslate-x uses wrapped up like this:
[fusion_text][:de][/fusion_text]
Forum: Plugins
In reply to: [qTranslate X] qTranslate-X and Fusion Page BuilderRunning with 3.2.9.9.7 and the behaviour has changed from earlier versions but it’s still broken. 🙁 It doesn’t matter if I use the language switch buttons or the single language mode, the fusion page builder always displays all content of the page, i.e. I see every [:de] and [:en] on the page. That makes editing a bit tedious. On the plus side: Content gets saved, apparently. 🙂
Forum: Plugins
In reply to: [qTranslate X] qTranslate-X and Fusion Page BuilderHi Gunu,
thanks for the fast reply. I’ll clean out the current test setup and start over with a clean slate with the latest beta and get back to you.
I just found this thread after a lot of digging. I have the same effect with the latest 0.9.9.12 – and a live site where we can examine the problem together if you like, it is easy to provoke. I can even move it to a separate server for full logging if it needs be. This has been giving me a headache for a few days by now.
I am dying to test it. I have two installations which expose strange behaviour after enabling wp-piwik: Parts of the dashboard come up in plain text (content-type erroneously “text/plain” instead of “text/html”). Frontend is not affected, but that’s not quite a solace. I haven’t had time to investigate further, but I’d be happy to test some alpha (under NDA if necessary) or something, if you have anything to test.
Same behaviour here with current 5.5.3. Any idea what to look at?