Hello, I am running 6.6.2 and trying to access 6.7. I have the settings set to Beta/Bleeding Edge and the WP Updater is showing no updates available. Any idea what might causing this? Thank you
]]>In the WP dashboard widget, the following error is being shown:
Warning: Undefined property: stdClass::$version in /wp-content/plugins/wordpress-beta-tester/src/WPBT/WP_Beta_Tester.php on line 306In the Beta Testing menu item under tools, the following error is being shown:
Warning: Undefined property: stdClass::$version in /wp-content/plugins/wordpress-beta-tester/src/WPBT/WPBT_Core.php on line 172I’m using PHP 8.1.28 and WP 6.7-beta2-59226 and WordPress Beta Tester 3.6.0
]]>On update, the page that is returned that shows actions stops at “updating database”. If that’s the last operation, cool, but there’s no indication that anything happens after that, or that the operation is done/complete.
TY
Hello,
I’ve recently updated to WP 6.4-RC1 using your plugin, but then, after disabling it and heading to the WordPress Updates screen in the admin the update button says “Update to latest 6.5 nightly” instead of “Update to latest 6.4 nightly”. This didn’t happen before. When you updated to a RC version, the button only allowed you to update to nightlies and RCs in the same version.
Has the plugin changed in a recent update?
]]>I have the following settings selected on /wp-admin/tools.php?page=wp-beta-tester
and the message displayed is
Currently your site is set to update to version 6.2.3, 6.3-RC1, or 6.3, whichever is released first.
However, when I go to /wp-admin/update-core.php the button says
Update to version 6.3-RC2
and 6.3-RC2 is not one of the options listed on the first page.
I would like to remove the link to “Report a Bug” in the Admin Toolbar as I’m using Beta-Versions and RCs for screenshots.
Is there a way to do that other than display: none with CSS?
While I’m using Opera, the debug info to send a debug report shows this:
=== Environment
– WordPress: 6.3-alpha-56027
– PHP: 8.1.9
– Server: nginx/1.16.0
– Database: mysqli (Server: 10.4.10-MariaDB / Client: mysqlnd 8.1.9)
– Browser: Chrome 113.0.0.0 (Windows 10/11)
My browser is Opera. My user agent string is:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36 OPR/99.0.0.0
While when I open Chrome, it’s:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36
So, then Opera is missing.
I wonder if this is going to be a glitch for all Chromium based browsers.
]]>I’d love to see in a future version the build time & date of the alpha… This way I can more easily see which commits are already in there and which ones not.
]]>Uhhhhh…
Fatal error: Uncaught Error: Call to undefined function wp_is_mobile() in /Users/vicki.farmer/Sites/wp.local/wp-content/plugins/wordpress-beta-tester/src/WPBT/WPBT_Bug_Report.php:242 Stack trace: #0 /Users/vicki.farmer/Sites/wp.local/wp-content/plugins/wordpress-beta-tester/src/WPBT/WPBT_Bug_Report.php(127): WPBT_Bug_Report->set_browser() #1 /Users/vicki.farmer/Sites/wp.local/wp-content/plugins/wordpress-beta-tester/src/WPBT/WPBT_Bug_Report.php(78): WPBT_Bug_Report->set_environment_data() #2 /Users/vicki.farmer/Sites/wp.local/wp-content/plugins/wordpress-beta-tester/src/WPBT/WPBT_Settings.php(50): WPBT_Bug_Report->__construct(Object(WP_Beta_Tester), Array) #3 /Users/vicki.farmer/Sites/wp.local/wp-content/plugins/wordpress-beta-tester/src/WPBT/WP_Beta_Tester.php(65): WPBT_Settings->run() #4 /Users/vicki.farmer/Sites/wp.local/wp-content/plugins/wordpress-beta-tester/src/WPBT/WPBT_Bootstrap.php(56): WP_Beta_Tester->run() #5 /Users/vicki.farmer/Sites/wp.local/wp-content/plugins/wordpress-beta-tester/wp-beta-tester.php(34): WPBT_Bootstrap->run() #6 /Users/vicki.farmer/Sites/wp.local/wp-settings.php(398): include_once(‘/Users/vicki.fa…’) #7 /Users/vicki.farmer/Sites/wp.local/wp-config.php(294): require_once(‘/Users/vicki.fa…’) #8 /Users/vicki.farmer/Sites/wp.local/wp-load.php(50): require_once(‘/Users/vicki.fa…’) #9 /Users/vicki.farmer/Sites/wp.local/wp-admin/admin.php(34): require_once(‘/Users/vicki.fa…’) #10 /Users/vicki.farmer/Sites/wp.local/wp-admin/index.php(10): require_once(‘/Users/vicki.fa…’) #11 {main} thrown in /Users/vicki.farmer/Sites/wp.local/wp-content/plugins/wordpress-beta-tester/src/WPBT/WPBT_Bug_Report.php on line 242
]]>WordPress Multisite.
Beta Testing Page Settings:
Bleeding Edge & Beta/RC Only
“Please note:?There are no development builds available for the beta stream you have chosen, so you will receive normal update notifications.”
Updates Screen:
Current version: 6.1.1
Last checked on March 6, 2023 at 5:20 pm GMT+0000. Check again.
This site is automatically kept up to date with each new version of WordPress.
You have the latest version of WordPress.
Any ideas? Thanks!
]]>When activating the plugin following in PHP 8.2 with WP 6.2-beta-1
Deprecated: Creation of dynamic property WPBT_Extras::$wp_beta_tester is deprecated in?C:\xampp\htdocs\wp\wp-content\plugins\wordpress-beta-tester\src\WPBT\WPBT_Extras.php?on line?44
Deprecated: Creation of dynamic property WPBT_Extras::$wp_beta_tester is deprecated in?C:\xampp\htdocs\wp\wp-content\plugins\wordpress-beta-tester\src\WPBT\WPBT_Extras.php?on line?44
Also In a fresh installation, installing the WordPress Beta Tester plugin and then upgrading to WP 6.2-beta-1 and disable and then activate the plugin following accours:
The plugin generated 654 characters of?unexpected output?during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.
]]>The last autoupdate took down site with:
PHP Fatal error: ?Uncaught TypeError: Return value of Composer\\
Autoload\\ClassLoader::initializeIncludeClosure() must be an instance of Composer\\Autoload\\void, none returned in …/wp-con
tent/plugins/wordpress-beta-tester/vendor/composer/ClassLoader.php:580\nStack trace:\n#0 …/wp-content/plugins/wordpress-beta
-tester/vendor/composer/ClassLoader.php(112): Composer\\Autoload\\ClassLoader::initializeIncludeClosure()\n#1 …/wp-content/p
lugins/wordpress-beta-tester/vendor/composer/autoload_real.php(28): Composer\\Autoload\\ClassLoader->__construct(‘……’)\n#2 …/wp-content/plugins/wordpress-beta-tester/vendor/autoload.php(25): ComposerAutoloaderInit248763277659ec81f8c4ff690d89804d::getLoad
er()\n#3 …/wp-content/plugins/wordpress-beta-tester/wp-beta-tester.php(33): require_once(‘……’)\n#4 …/wp-settings.php(447): include_once(‘…..’)\n#5 …/wp-config.php(76) in …/w
p-content/plugins/wordpress-beta-tester/vendor/composer/ClassLoader.php on line 580
Not immediately obvious to me why. Moving the WordPress-beta=-tester plugin out the way got the site back, but no time to troubleshoot today.
php 7.0.33
With WordPress Beta Tester plugin activated the /wp-admin/index.php home dashboard gives a PHP 8.1 warning.
Deprecatedpreg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated
wp-includes/kses.php:1729
preg_replace()
wp-includes/kses.php:1729
wp_kses_no_null()
wp-includes/kses.php:752
wp_kses()
wp-includes/kses.php:2151
wp_kses_post()
wp-content/plugins/wordpress-beta-tester/src/WPBT/WP_Beta_Tester.php:301
WP_Beta_Tester->beta_tester_dashboard()
wp-admin/includes/template.php:1410
do_meta_boxes()
wp-admin/includes/dashboard.php:271
wp_dashboard()
wp-admin/index.php:203If the plugin is not activated the warning is not thrown in home. Only some other places https://core.trac.www.ads-software.com/ticket/57578#ticket
Can the Tested up to: be bumped up also ?? Thanks
]]>On every update all the themes from twenty ten up to twenty twenty three are again downloaded, even when i use only twenty three. Is there any way how to block this?
]]>
preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated
When I activate the plugin with my local setup running PHP 8.1, then I get a whole bunch of these deprecation warnings:
Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /app/wordpress/wp-includes/Requests/Cookie/Jar.php on line 63
Not a major issue, just thought I should report it!
]]>After the last update (v3.1.3) I get locked out from WP admin if WP Beta Tester plugin is active. I had to deactivate it through FTP by removing the plugin folder.
I created a debug backtrace which also includes WP Beta Tester at some level:
https://pastebin.com/vV1T444Z
There are two line in the debug.log related to this:
[24-Sep-2021 07:31:29 UTC] PHP Warning: Use of undefined constant SECURE_AUTH_COOKIE – assumed ‘SECURE_AUTH_COOKIE’ (this will throw an Error in a future version of PHP) in /home/myhomedir/mysite.tld/wp-includes/pluggable.php on line 847
[24-Sep-2021 07:31:29 UTC] PHP Warning: Use of undefined constant LOGGED_IN_COOKIE – assumed ‘LOGGED_IN_COOKIE’ (this will throw an Error in a future version of PHP) in /home/myhomedir/mysite.tld/wp-includes/user.php on line 532
You can see the backtrace for the first error message. I assume the second message is somehow related.
]]>Received this PHP error just now, thought the devs would like to be aware:
PHP Warning: Undefined array key 1 in /../../wp-content/plugins/wordpress-beta-tester/src/WPBT/WPBT_Core.php on line 385
My issue is similar to the issue addressed here. Since the original author hasn’t updated yet, I am redoing every task as he mentioned and pasting the Request and API Response using https://www.ads-software.com/plugins/updates-api-inspector/ plugin.
My current version is 5.7.3-alpha-51171
Request code
array(
'timeout' => 3,
'user-agent' => 'WordPress/5.7.3-alpha-51171; https://wpdemo.local/',
'headers' => array(
'wp_install' => 'https://wpdemo.local/',
'wp_blog' => 'https://wpdemo.local/',
),
'body' => array(
'translations' => array(),
),
'query_string' => array(
'version' => '5.8-alpha',
'php' => '7.3.5',
'locale' => 'en_US',
'mysql' => '8.0.16',
'local_package' => '',
'blogs' => '1',
'users' => '1',
'multisite_enabled' => '0',
'initial_db_version' => '49752',
'channel' => 'development',
),
)API response
array(
'offers' => array(
array(
'response' => 'development',
'download' => 'https://www.ads-software.com/nightly-builds/wordpress-latest.zip',
'locale' => 'en_US',
'packages' => array(
'full' => 'https://www.ads-software.com/nightly-builds/wordpress-latest.zip',
'no_content' => false,
'new_bundled' => false,
'partial' => false,
'rollback' => false,
),
'current' => '5.8-beta3-51218',
'version' => '5.8-beta3-51218',
'php_version' => '5.6.20',
'mysql_version' => '5.0',
'new_bundled' => '5.6',
'partial_version' => false,
),
array(
'response' => 'latest',
'download' => 'https://downloads.www.ads-software.com/release/wordpress-5.7.2.zip',
'locale' => 'en_US',
'packages' => array(
'full' => 'https://downloads.www.ads-software.com/release/wordpress-5.7.2.zip',
'no_content' => 'https://downloads.www.ads-software.com/release/wordpress-5.7.2-no-content.zip',
'new_bundled' => 'https://downloads.www.ads-software.com/release/wordpress-5.7.2-new-bundled.zip',
'partial' => false,
'rollback' => false,
),
'current' => '5.7.2',
'version' => '5.7.2',
'php_version' => '5.6.20',
'mysql_version' => '5.0',
'new_bundled' => '5.6',
'partial_version' => false,
),
array(
'response' => 'autoupdate',
'download' => 'https://www.ads-software.com/nightly-builds/wordpress-latest.zip',
'locale' => 'en_US',
'packages' => array(
'full' => 'https://www.ads-software.com/nightly-builds/wordpress-latest.zip',
'no_content' => false,
'new_bundled' => false,
'partial' => false,
'rollback' => false,
),
'current' => '5.8-beta3-51218',
'version' => '5.8-beta3-51218',
'php_version' => '5.6.20',
'mysql_version' => '5.0',
'new_bundled' => '5.6',
'partial_version' => false,
'new_files' => true,
),
),
'translations' => array(),
)Update
5.8 is finally installed. Seems like the installation process took a long time. So closing the topic and changing the status as solved.
]]>Selecting “Bleeding Edge” and “Beta/RC Only” shows that I should be able to update to 5.8-beta1:
Currently your site is set to update to version 5.8-beta1, 5.8-RC1, or 5.8, whichever is released first.
But I only end up with version 5.7.1.
I also tried, installing an older version, then using beta tester to update – no go. I also tried installing 5.8-beta1 manually, downgraded, then tried to update back to 5.8-beta1 – not working also.
]]>Hi. Today is 2 February, where WP 5.7 beta 1 is going to be released. I checked update core, but the beta wasn’t there yet. Can you check what’s happening? Thanks.
]]>Hi, after I update to latest alpha of WordPress 5.7, I realized all default WordPress themes got installed
Is WordPress beta package always contains that?
Notice: Undefined property: stdClass::$version in ..\wp-admin\includes\update.php on line 251
WP_Beta_Tester->update_footer( )
]]>Hi,
I would like to check my theme/plugin in the new WP (5.6), so I have installed the WordPress Beta Tester plugin at my local install.
But to be honest, for someone who’s not a full time developer it’s kind of difficult to understand the meaning of the settings (Beta/RC Only, Release Candidates Only, Bleeding edge, etc). Although there’s some explanation added, it’s still quite vague. So when hitting the “Update” button, it’s always a suprise which version is being installed.
I would like to see a setting that says “Update to most recent beta version (5.6)”, or something similar. For dummies like me ??
Guido
]]>There is no way to test WordPress 5.6 anymore. Upgrade to Channel Bleeding edge -> Nightlies ends in WordPress 5.7.
]]>Hi,
Quick question if I was to use release candidate on live site and the official version was released can I update from the RC to Official?
?f so how is this done?
Thanks
Leo
]]>WordPress Beta Tester version 3.0.3
From help panel:
When switching between Point release and Bleeding edge you will need to set the stream option to Nightlies then update to get on that channel, then set to another stream option ( Beta/RC Only or Release Candidates Only ) if desired.
First I had the stream Bleeding edge -> Nightlies and the recent version 5.6 beta 4 – 49607.
Second I wanted to switch to the Point release channel. I did, as described in the help panel and activated Point release and Nightlies and saved changes.
After saving the Plugins shows me 3 notices.
1.) Saved. Why don’t you head on over and upgrade now.
2.) Warning about database and downgrade
3.) Warning: Your current WordPress Beta Tester plugin configuration will downgrade your installation to a previous version – please reconfigure it.
Question to 1.) Why it says upgrade and not downgrade?
Since the WordPress did not change after saving I clicked the only available option ->
upgrade now (from notice 1.))
On the following page I clicked on the blue Update now button, which is below the sentence/hint:
You are using a development version of WordPress. You can update to the latest nightly build manually:
But, nothing changes. Still version 5.6 beta 4 ….
Back to the plugin settings page. I have made a screenshot and flagged the conflicting informations.
https://share.getcloudapp.com/NQu1yj5B
In my opinion and understanding, if I switch to Point release and the stream nightlies I should receive the recent dev version of the upcoming next minor version of WordPress in this case 5.5.4 xx.xx.
Is this a bug that I still have the beta of upcoming Major version after I switched to the point release channel?
]]>Hello there,
i have a serious issue with WordPress after updating to 5.5.
Some of them have switched to alfa versions without my intervention. I did not opt for alpha, they are working / production sites and i really don’t need alpha versions and daily updates in the middle of the day with customers logged in. Most of them are old installs from 2014-18, updated regulary and well maintained.
Also, for some of them i got back old themes from 2012, 2013, up to 2020.
This is strange and i don’t know how to stop the automatic updates.
I have about 30-40 wp installs waiting to be updated to 5.5 but with this problem i’m not in the mood for more problems.
Please, anyone else had this problem after 5.5 update?
Thanks.
]]>Please can you advise how to resolve this issue that I’m getting using your plugin in the last few days.
When logged in we see a notification “Your current WordPress Beta Tester plugin configuration will downgrade your install to a previous version – please reconfigure it.”
Now, I’m receiving an alert email from Wordfence with the info:
=======================================================
Alert generated at Saturday 25th of April 2020 at 10:28:54 PM
High Severity Problems:
* Your WordPress version is out of date
=======================================================
We are using the ‘Point release nightlies’ option in your plugin.
Thanks greatly, best wishes
]]>Hello ?
it’s me again.
I have tested now, what happens, when I have activated Beta/RC - Bleeding edge. Yesterday the upgrade started from version (5.4-RC1-47424) and great! it upgraded to 5.4-RC2 – as expected.
After this, I activated Bleeding egde nightlies and it upgraded to (5.4-RC2-47447).
Third test: Activation of Beta/RC - Bleeding edge again but … I can’t restore to version 5.4-RC2.
It seems to me, that once you have started the bleeding edge nightlies stream you will not be able to restore to the recent RC (or beta) version. You must wait until the next RC or Beta is released. In this case, I must wait for the release of 5.4 RC 3.
In my opinion, this cannot be the desired behaviour. Beta/RC - Bleeding edge is for RC/beta testing and it should always be possible to test a real Beta/RC version.
Am I wrong or should I open an issue on github?
]]>