AlphaK
Forum Replies Created
-
Found!
In admin/publish.php the whole post goes into the $description variable, which cannot be longer than 10000 characters, as the API says.Shortening the description to 10000 or less (using e.g. xyz_fbap_string_limit function) solves this issue.
Forum: Plugins
In reply to: [YARPP - Yet Another Related Posts Plugin] YARPP working with InnoDBIndeed that feature would be nice (just joining the request pool).
Forum: Plugins
In reply to: [W3 Total Cache] W3 Total Cache does dot appear in my plugin listOK, seems to be linked to the fact I run a multisite installation.
Tested on another WP3.6 install from scratch, plugin is visible. I do not activate it. As soon as I activate the network, plugin is not visible in the plugin list anymore.
Could fixing be considered?
Forum: Plugins
In reply to: [Advanced Editor Tools] Editor broken when using CDN admin menu over HTTPSThanks for the reply. I have a better overview now.
I have actually found an easy workaround, which I applied as soon as I could: only declare the CDN when the connection is in play text (not over HTTPS). As in my case resources can be downloaded either from the CDN domain, either from the original domain, having an HTTPS connection just makes WP believe this is a standard installation with no CDN at all.
Here’s a sniplet of my wp-config.php:
if(!isset($_SERVER['HTTPS'])) { define('WP_CONTENT_URL', 'https://cdn.mydomain.com/wp-content'); }But I like perfection and hope this hack can be removed one day ^^, so I’ll probably have a closer look on TinyMCE 4.0 when it comes to WordPress.
Thanks for the support, I’ll contact you offline with more details.
It might take some days, as I’m a bit busy currently.n.b. I noticed similar issues for other plugins and am beginning to think it is a WP core issue, many searches including keywords WP_CONTENT_URL and FORCE_SSL_ADMIN show a lot of know issues that seem to be causing headaches to a lot of people :/
For the moment the 2 lines commented out seems to be a nice fix. I did not have any error log since that time.
Almost solved.
The real culprit was actually my CDN that I set up at the same time. It does not deliver content over HTTPS.
I don’t really get why the result differ according to the activation or deactivation of WP to Twitter, anyway. If you have any idea, it might help ??I commented out the 2 lines concerning $fb_group_list[], by the way. I will check my log file (it’s emailed to me every night if it is not empty ??
Actually I have error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED, so E_STRICT was already disabled. I checked by echoing error_reporting on a WordPress page (in case it is modified by any plugin), it is set to 4983. So E_STRICT is indeed disabled.
I understood that part of E_STRICT is now integrated into E_ALL in PHP 5.4, but could not guess what part exactly yet.
I set those values because php.ini recommended E_ALL & ~E_DEPRECATED & ~E_STRICT for a production server, and then removed also E_NOTICE because it was giving too much errors for other websites.
Thanks, done. I have patched the code and will give a try.
Well about the STRICT error reporting, I don’t know if a lot of people use it. But as Wordbooker is the only plugin giving me this kind of errors, I’ll keep the setting for the moment and hope it won’t take too much of effort to fix those little annoyances ??
Hello Steve.
I installed recently last version 2.1.35 and saw your fix was included.Unfortunately the issue has appeared at other places now.
[03-Aug-2013 10:18:03 UTC] PHP Warning: Creating default object from empty value in /path/to/www/wp-content/plugins/wordbooker/includes/wordbooker_cron.php on line 175 [03-Aug-2013 11:10:47 UTC] PHP Warning: Creating default object from empty value in /path/to/www/wp-content/plugins/wordbooker/includes/wordbooker_cron.php on line 144Regards
Forum: Plugins
In reply to: [WP Minify] [WP-Minify] 1.1 is brokenStill broken for me with version 1.1.3 : still having a HTTP/1.0 400 Bad Request when trying to get a minify link.
The problem appears only when the option box [Don’t use “pretty” URL] is unchecked, however. If this option is checked, my theme is displayed properly.Forum: Plugins
In reply to: [WP Minify] [WP-Minify] 1.1 is brokenAndreas, same for me.
Going to revert to previous version.Going manually to the minified URL gives me a 400 Bad request
Huge history as I can see.
Again in XHTML 1.1 none of the mandatory child element of the
<head>tag support aclassattribute.Then I may suggest 2 workarounds :
First one : to cycle manually through meta tags until the one which attribute
nameequalssyntaxhighlighter-versionis found. There we can insertcorecssandthemecssjust before.Second one : to do the same but using WordPress’s internal jQuery to catch the correct tag using a direct selector, that would look like :
$('meta[@name="syntaxhighlighter-version"]')Both solutions may imply a loss of performance during the script load, but negligible I assume.
OK. If my understanding is correct, you use it in the following code :
document.getElementsByTagName("head")[0].insertBefore( corecss, document.getElementById("syntaxhighlighteranchor") );Then why not adding your stylesheets at the end of the head element ? Then there is no need for an id nor a class. This code might do the trick :
document.getElementsByTagName("head")[0].appendChild(corecss);