Meska_
Forum Replies Created
-
Yes perfect. Everything seems to be working again.
Hi,
thanks for sending version 3.2.6.
I checked the package, and the previous
WP_Errornamespace issue appears to be fixed correctly:$errors = new \WP_Error();However, version 3.2.6 still contains the unexpected-output problem that can prevent WordPress from setting login cookies and can corrupt AJAX or REST responses.
In around 30 PHP files, the following pattern is still present:
<?php if ( ! defined( 'ABSPATH' ) ) exit; ?> <?phpThe closing
?>followed by a new PHP block outputs the line break between the blocks.One directly affected file is:
includes/class-xoo-el-helper.phpThis file produces a CRLF line break before WordPress can send HTTP headers. This can cause:
- “Cookies are blocked due to unexpected output”
- failed WordPress logins
- broken AJAX or REST responses
- blank or incomplete WordPress admin pages
The direct-access guard should remain within the same PHP block:
<?php if ( ! defined( 'ABSPATH' ) ) { exit; }Please check the entire plugin package and remove the closing and reopening PHP tags from all affected files, not only one specific file.
I tested a locally corrected version with all affected transitions removed, and it no longer produces unexpected output.
Hi,
unfortunately, version 3.2.5 introduces another critical regression.
After updating from 3.2.4 to 3.2.5, WordPress login fails with the following message:
Error: Cookies are blocked due to unexpected output.
The same unexpected output also causes several WordPress admin pages to load as blank or incomplete pages.
Reverting to version 3.2.4 immediately resolves the issue.
I compared both plugin versions and found the cause. In version 3.2.5, at least 37 PHP files now begin with this pattern:
<?php if ( ! defined( 'ABSPATH' ) ) exit; ?> <?phpOne affected file is:
includes/xoo-framework/xoo-framework.phpBecause the first PHP block is closed with
?>, the line breaks between the two PHP blocks are sent as output. Sincexoo-framework.phpis loaded during normal plugin initialization, output is generated before WordPress can send login cookies and HTTP headers.The guard should remain inside a single PHP block, for example:
<?php if ( ! defined( 'ABSPATH' ) ) { exit; }The file should then continue without closing and reopening PHP.
Please check all files where the new direct-access protection was added. The problem is not limited to one template file; the same pattern occurs throughout the plugin package.
This appears to have been introduced as part of the security-related changes in 3.2.5.
For context, the previous release already caused customer registration to fail because
WP_Errorwas referenced inside theXooEL\Affnamespace without the global namespace prefix. You provided version 3.2.4 after I reported that issue, and that version currently works.Could you please release a corrected update that includes both fixes and test the following before publishing it?
- WordPress login via
/wp-login.php - WooCommerce customer registration
- Easy Login AJAX registration
- WordPress admin React pages
- AJAX and REST responses
- PHP 8.4 compatibility
Thanks.
@pulkitxootix great. thank you
Seems to work, thx
Forum: Plugins
In reply to: [WP Discord] Bot Offline, not postinghm, still nothing.
I even created a new bot and did all the steps again. Still doesn’t work.
https://de.wordpress.org/plugins/wp-discord-post/ <- works like a charm – maybe you create a plugin together 😛Forum: Plugins
In reply to: [WP Discord] Bot Offline, not postingokay it looks like it was removing every . and _ as soon as i was saving the settings. Gonna try it later.
Forum: Plugins
In reply to: [WP Discord] Bot Offline, not postingits all set up correctly. i tried a other plugin and its working. :/
Forum: Plugins
In reply to: [WP Discord] Bot Offline, not postingYeah I did everything correctly. But there is no wordpress webhook or something, I guess it should create one, no?
Forum: Plugins
In reply to: [Polylang] Infinite scroll only works on mainlanguageokay looks like it works. forgot to clean the cache of the browser 😀 ty.
Forum: Plugins
In reply to: [Polylang] Infinite scroll only works on mainlanguageHm still the same. Gonna have a look how its added in the TT and TF Themes, but should be the same, since its done using this guide: https://jetpack.me/support/infinite-scroll/
maybe the slug is missing or something… in the “get_posts” idk
Forum: Plugins
In reply to: [Polylang] Infinite scroll only works on mainlanguagejetpack ofc. jetpack is a most have so ;D … i dont know why it doesnt work at the 2nd page.