rockschtar
Forum Replies Created
-
Hello Farhan,
I tested it with a fresh WordPress 6.8 installation, using Ultimate Block 3.3.0 as the only installed plugin. When setting WP_DEBUG to “true” in wp-config.php, the following error appears on all pages:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the
ultimate-blocksdomain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at theinitaction or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /app/wp-includes/functions.php on line 6121I reviewed your plugin code, and it’s quite obvious what happens. The entire plugin loads via the “plugins_loaded” hook, which also loads the text domain. This is incorrect since WordPress 6.7. Translations should be loaded no earlier than the “init” hook action.
Are there any updates on this issue? The error persists in Version 3.3.0 with WordPress 6.8.
Forum: Plugins
In reply to: [TinyMCE Comment Field - WYSIWYG] GDPRTinyMCE Comment Field uses Google Fonts. I think that is the only issue with GDPR.
Hallo,
habe das gleiche Problem gehabt seit einem Upgrade auf PHP7.0 bzw. auf 7.1. Nach ein klein wenig debugging habe ich aber den Fehler gefunden.
Der Fehler liegt in der Methode cron_active der Klasse BackWPup_Cron. Diese Methode erwartet den Parameter $args als Array. Beim manuellen starten eines Jobs wird als Parameter $args aber ein leerer String übergeben was dann zu Folgefehlern führt. Am Ende wird der Job nicht ausgeführt und kein Logfile geschrieben. Daraus resultiert dann die Fehlermeldung “BackWPup-Auftrag startet nicht”….Hoffe diese Information hilft den Entwicklern das Problem zu fixen.
- This reply was modified 9 years, 2 months ago by rockschtar.
Forum: Plugins
In reply to: [W3 Total Cache] Old gziped css files are delivered as ‘application/x-trash’Same here. Happens randomly on different WordPress Sites. Thanks for the workarround.
Forum: Plugins
In reply to: [TinyMCE Comment Field - WYSIWYG] Conflit with Widget functionalityHi,
thanks for the information. This is a bug in current Titan Framework version.
I added a workarround for this in version 1.8.3. Please update to this version.Forum: Plugins
In reply to: [TinyMCE Visual Editor Comment] Cannot Save A Comment Typed In EditorI think there is something wrong implemented in your theme. Try to activated the WordPress default theme and check if the error still exists.
Forum: Reviews
In reply to: [TinyMCE Comment Field - WYSIWYG] WYSIWYG comment writing done rightThank you for taking the time to post a rating. I’m glad you found the plugin useful.
Forum: Plugins
In reply to: [TinyMCE Comment Field - WYSIWYG] Authors and Administrator ProblemBug fixed in version 1.8.
Forum: Plugins
In reply to: [TinyMCE Comment Field - WYSIWYG] Embed doesn't work correctly?Check out the new version. I added an option for enabling auto embedding.
.
Please check out Version 1.6. Problem with “The plugin does not have a valid header” should be solved.
If you don’t see the tinymce comment box on your desktop theme, hen something is incorrectly implemented in your theme. To check this, simply activate a wordpress default theme an see if tinymce comment field works.
Forum: Plugins
In reply to: [TinyMCE Comment Field - WYSIWYG] Not available to anonymous users?This Plugin works for anonymous users as well. Maybe another Plugin is blocking something?
Forum: Plugins
In reply to: [TinyMCE Comment Field - WYSIWYG] Server ErrorI need more details about the error message. Maybe you can turn on WP_Debug to get a more detailed error message.
I tested the plugin down to PHP Version 5.4 and it should be working.
Forum: Plugins
In reply to: [TinyMCE Comment Field - WYSIWYG] Not working in chromeTested it in latest Chrome Version (48.0.2564.116m) and it works fine. Maybe a problem with an Extension?