bluebeard2
New member
- May 2, 2022
- 1
- 0
- 1
was wondering what I was missing. thanks for the hint. good until 20482024![]()
was wondering what I was missing. thanks for the hint. good until 20482024![]()
Just installed this one and it still comes up with the notice asking for the keyOkay, I guess I did it. Here's the nulled version WP Staging Pro v4.2.4 Nulled
@ChariotsOfThyer Go to the license section and click ActivateJust installed this one and it still comes up with the notice asking for the key
You hero, thank you@ChariotsOfThyer Go to the license section and click Activate
Bud1 tsIlocblob
@assetsIlocblobA.������autoloader.phpIlocblob�.������BackendIlocblob.������Backendbwspblob�bplist00�
]ShowStatusBar[ShowToolbar[ShowTabView_ContainerShowSidebar\WindowBounds[ShowSidebar _{{675, 317}, {803, 422}} #/;R_klmnbootstrap.phpIlocblob�.������constantsPro.phpIlocblob�.������CoreIlocblobA�������Deactivate.phpIlocblob�������� FrameworkIlocblob������FrontendIlocblob��������
install.phpIlocblob�������� languagesIlocblobA������opcacheBootstrap.phpIlocblob�������ProIlocblob������proBootstrap.phpIlocblob�������
uninstall.phpIlocblob�~������imeRequirements.phpIlocblobA~������
vendor_wpstgIlocblob~������wp-staging-error-handler.phpIlocblob�~������wp-staging-pro.phpIlocblob�~������
E
./.DS_Store
./Backend/.DS_Store
./Backend/Pro/.DS_Store
@gpLover!What really grinds my gears is the weird stuff inside those ZIPs.
This one contains ".DS_Store"
here
Code:./.DS_Store ./Backend/.DS_Store ./Backend/Pro/.DS_Store
And after activation I see:
This version of WP STAGING | PRO has not been tested with WordPress version 6.0.
Kinda funny the purpose of the plugin is to run tests before updating a live system and you cant use said tool because it is not compatible with the software thats it supposed to test. full circle.
Here's v4.2.6 Nullednot checked by me. , please check it
v.4.2.6
Download WP Staging Pro v4.2.6 - One-Click Solution for Creating Staging Sites Nulled Free
= v4.2.6 =
* Fix: Certain default plugins like wps-hide are not excluded anymore during cloning #1742
* Fix: Scheduled backup not always executed #1754
* Fix: Backup folder is deleted during backup restore on Windows OS #1737
* Fix: On backup restore retry deleting an item again in next request instead of re adding it at the end of queue, if item isn't completely deleted in current request #1758...
Download WP Staging Pro v4.2.8 - One-Click Solution for Creating Staging Sites Nulled Free
= v4.2.8 =
* Fix: On some servers, autoloader tries to load Composer\InstalledVersions although this doesn't exist. We fix this by only loading classes that exist #1801
Click on settings and then under license tab click on activate license, if license is not pre-filled , fill any random number. It will remove the enter license notification, but under backup and migration it will still ask for license.Key dont active
public function isValidOrExpiredLicenseKey()
{
return true;
if (!($licenseData = get_option(self::WPSTG_LICENSE_STATUS))){
return false;
}
if (isset($licenseData->license) && $licenseData->license === 'valid'){
return true;
}
if (isset($licenseData->error) && $licenseData->error === 'expired'){
return true;
}
return false;
}
Going to file wp-staging-pro/Backend/Pro/Licensing/Licensing.php
looking for if (!($licenseData = get_option(self::WPSTG_LICENSE_STATUS)))
add return true; before that line. It will look something like this one:
PHP:public function isValidOrExpiredLicenseKey() { return true; if (!($licenseData = get_option(self::WPSTG_LICENSE_STATUS))){ return false; } if (isset($licenseData->license) && $licenseData->license === 'valid'){ return true; } if (isset($licenseData->error) && $licenseData->error === 'expired'){ return true; } return false; }
= 4.2.10 =
* Fix: Important update! Deselecting all tables does not lead to exclusion of tables as expected, but leads to selection of all tables. Thus all tables are copied and possibly overwritten instead of deselected. Applies to new cloning, UPDATE and RESET of a staging page. That can lead to data loss in the staging site. An update is strongly recommended! The problem appeared for the first time in version