Fabian
Forum Replies Created
-
Forum: Plugins
In reply to: [Yoast SEO] Breadcrumbs incompatible with qTranslate in version 14.1Thanks @mikes41720, I created https://github.com/Yoast/wordpress-seo/issues/15186
Yes reverting to the previous version fixes it.- This reply was modified 4 years, 10 months ago by Fabian.
Forum: Plugins
In reply to: [Yoast SEO] Breadcrumbs incompatible with qTranslate in version 14.1I used the latest version for qtranslate, wordpress and yoast.
I have reverted to 14.0.4 and it fixed the issue so definitely there is something with the new version of yoast.It did not for me ?? Exactly the same error with 14.0.2.
I am using W3 Total Cache, could it be related?It does not work for me either with the hotfixes.
In the JS console I have the following 2 errors:
wp-seo-indexation-1401.js?ver=14.0.1:1 GET https://xxxx/wp-json/yoast/v1/indexation/posts 404 wp-seo-indexation-1401.js?ver=14.0.1:1 TypeError: Cannot read property 'length' of undefined at wp-seo-indexation-1401.js?ver=14.0.1:1 at tryCatch (wp-polyfill.min.js:1) at Generator.invoke [as _invoke] (wp-polyfill.min.js:1) at Generator.t.<computed> [as next] (wp-polyfill.min.js:1) at r (wp-seo-indexation-1401.js?ver=14.0.1:1) at wp-seo-indexation-1401.js?ver=14.0.1:1
When I manually do a GET on https://xxxx/wp-json/yoast/v1/indexation/posts I have 404 with the JSON content:
{"code":"rest_no_route","message":"No route was found matching the URL and request method","data":{"status":404}}
- This reply was modified 4 years, 10 months ago by Fabian.
Forum: Plugins
In reply to: [Yoast SEO] YOAST 14.0 Cannot complete indexation processSorry I posted on the wrong topic. My indexation process did not start at all which is a different issue. I cannot delete this post but I will post on https://www.ads-software.com/support/topic/something-went-wrong-while-optimising-the-seo-data-of-your-site-please-try-agai/ as it makes more sense there ??
It does not work for me either with the hotfixes.
In the JS console I have the following 2 errors:
wp-seo-indexation-1401.js?ver=14.0.1:1 GET https://xxxx/wp-json/yoast/v1/indexation/posts 404 wp-seo-indexation-1401.js?ver=14.0.1:1 TypeError: Cannot read property 'length' of undefined at wp-seo-indexation-1401.js?ver=14.0.1:1 at tryCatch (wp-polyfill.min.js:1) at Generator.invoke [as _invoke] (wp-polyfill.min.js:1) at Generator.t.<computed> [as next] (wp-polyfill.min.js:1) at r (wp-seo-indexation-1401.js?ver=14.0.1:1) at wp-seo-indexation-1401.js?ver=14.0.1:1
When I manually do a GET on https://xxxx/wp-json/yoast/v1/indexation/posts I have 404 with the JSON content:
{"code":"rest_no_route","message":"No route was found matching the URL and request method","data":{"status":404}}
- This reply was modified 4 years, 10 months ago by Fabian.
Forum: Plugins
In reply to: [Disqus Comment System] COMPATIBILITY WITH WORDPRESS V 5.0I have the same issue, I updated to WordPress 5.x and now I have issue with the API. I cannot sync comments in my case. Otherwise everything works fine. I created a thread about it 6 weeks ago but I did not receive answer ?? https://www.ads-software.com/support/topic/sync-not-working-7/
Forum: Plugins
In reply to: [Disqus Comment System] Sync not workingI still have the issue, the new comments on Disqus do not get added to my WordPress Database.
The fact that I have migrated to WordPress 5 last month make me wonder whether the plugin is ready for it… Can the developers check it?
Thanks!
Forum: Plugins
In reply to: [Social Icons Widget] Can you make the plugin PHP 7.0 compatible?Ah yes, you’re right! :S
Ignore my message…Forum: Plugins
In reply to: [List category posts] Compatibility with PHP tags inside the article bodyOk, I have the fix, use the tag [php] [/php] compatible with the PHP plugin and list category post. Now I have to update all my posts ?? but it’s working! ??
Forum: Plugins
In reply to: [List category posts] Compatibility with PHP tags inside the article bodyI was taking a look at the code, there is this function called content_getter in lcp-catlistdiplayer.php.
There should be a way to escape php tag somehow.Forum: Plugins
In reply to: [Exec-PHP] The plugin doesn't work on PHP version 7Well I have updated to ezPHP at the end, it is working well and compatible with PHP7. I guess this plugin is not maintained anymore.
Forum: Plugins
In reply to: [Broken Link Checker] PHP7 supportI plan a PHP7 migration as well. A new version that will be compatible with PHP7 will be nice.
Forum: Plugins
In reply to: [Exec-PHP] The plugin doesn't work on PHP version 7I will do the manual fix, but it will be great to have a new official version of this plugin!
I got the following report from another plugin:FILE: exec-php/includes/option.php
————————————————————————————-
FOUND 1 ERROR AFFECTING 1 LINE
————————————————————————————-
29 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
————————————————————————————-FILE: exec-php/includes/script.php
————————————————————————————-
FOUND 1 ERROR AFFECTING 1 LINE
————————————————————————————-
20 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
————————————————————————————-FILE: exec-php/includes/usermeta.php
—————————————————————————————
FOUND 1 ERROR AFFECTING 1 LINE
—————————————————————————————
24 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
—————————————————————————————FILE: exec-php/includes/config_ui.php
—————————————————————————————-
FOUND 1 ERROR AFFECTING 1 LINE
—————————————————————————————-
30 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
—————————————————————————————-FILE: exec-php/includes/cache.php
—————————————————————————————————————
FOUND 3 ERRORS AFFECTING 3 LINES
—————————————————————————————————————
20 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
22 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
39 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
—————————————————————————————————————FILE: exec-php/includes/runtime.php
————————————————————————————–
FOUND 1 ERROR AFFECTING 1 LINE
————————————————————————————–
21 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
————————————————————————————–FILE: exec-php/includes/style.php
————————————————————————————
FOUND 1 ERROR AFFECTING 1 LINE
————————————————————————————
12 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
————————————————————————————FILE: exec-php/includes/manager.php
—————————————————————————————————————
FOUND 5 ERRORS AFFECTING 5 LINES
—————————————————————————————————————
25 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
36 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
37 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
38 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
39 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
—————————————————————————————————————FILE: exec-php/includes/ajax.php
—————————————————————————————————————
FOUND 2 ERRORS AFFECTING 2 LINES
—————————————————————————————————————
21 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
64 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
—————————————————————————————————————FILE: exec-php/includes/write_ui.php
—————————————————————————————
FOUND 1 ERROR AFFECTING 1 LINE
—————————————————————————————
26 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
—————————————————————————————FILE: exec-php/includes/admin.php
—————————————————————————————————————
FOUND 7 ERRORS AFFECTING 7 LINES
—————————————————————————————————————
37 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
53 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
56 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
57 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
63 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
64 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
79 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
—————————————————————————————————————FILE: exec-php/includes/l10n.php
————————————————————————————————————————————-
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————————————————————-
33 | WARNING | Function name “__s” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
————————————————————————————————————————————-FILE: exec-php/includes/user_ui.php
————————————————————————————–
FOUND 1 ERROR AFFECTING 1 LINE
————————————————————————————–
23 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7
————————————————————————————–FILE: exec-php/exec-php.php
—————————————————————————————————————
FOUND 1 ERROR AFFECTING 1 LINE
—————————————————————————————————————
22 | ERROR | Assigning the return value of new by reference is deprecated in PHP 5.3 and forbidden in PHP 7.0
—————————————————————————————————————Forum: Plugins
In reply to: [Disqus Comment System] Translation not working anymoreOk, I finally found out. I was modifying the wrong line… I wonder how it was working before. Anyway, here is how to fix this and get the language with qTranslate:
Line 138, I have replaced
this.language = '<?php echo esc_js( apply_filters('disqus_language_filter', '') ) ?>';
With
this.language = '<?php echo qtrans_getLanguage() ?>';
It works like a charm now.
Forum: Plugins
In reply to: [Disqus Comment System] Translation not working anymoreI switched back to 2.82 but still the same error, the language does not change. I guess it is more a bug in the Disqus API. I hope they will fix it soon.