njweller

Hello @ravanh,

We have just released Jetpack Protect 3.1.1, which includes a fix for the undefined entrypoint constant. Thank you so much for the detailed reporting, and for your patience dealing with this issue!

Please let us know if you have any additional issues or questions!

Cheers,
Nate

Hello there Jason!

Do you know if your site currently has WP_DEBUG mode enabled? Turning off debug mode will ensure that warnings and deprecation notices like these are not displayed publicly to your users. I would recommend ensuring that the WP_DEBUG setting is set to false when your website is public facing/in production.

More information about editing this setting can be found here:
https://jetpack.com/blog/wp-config-php

For further context, deprecation notices like this appear to inform developers or site owners that a future version of software will include a change that will require it to be integrated differently in the future. It appears that the latest version of Jetpack Boost introduces a deprecation notice for a shared function that the core Jetpack plugin also uses – the next Jetpack update should resolve the deprecation notice and there is no danger to your site here.

Regardless, turning off debug logging on your site will ensure these messages are logged privately and not shown to your users.

I hope this information is useful, and please let me know if you have additional questions!

As an aside, to build on @charlesmdq answer – I would recommend keeping WP_DEBUG disabled when your site is in production, and only enabling it in testing and development environments. This ensures that PHP warnings and deprecation notices like these are not shown to your users.

More info on modifying this value can be found here: https://jetpack.com/blog/wp-config-php/

Hey there @greentp!

TLDR – you can turn off the Jetpack Custom CSS feature and still write custom styles for your site using the WordPress Customizer, without changing your theme.

The Appearance -> Additional CSS section will still work, and should take you to the following URL on your site: wp-admin/customize.php?autofocus[section]=custom_css

Any existing custom styles will still be available, but turning off the Jetpack feature will essentially remove support for using SCSS/LESS in your custom CSS, and the ability to completely disable the current theme’s styles.

*If you are currently using SCSS/LESS in your custom styles, I would recommend converting them to standard CSS before turning off the Jetpack feature.

For context, Jetpack added this custom CSS feature a long time ago, back when WordPress didn’t offer this built-in. We had some extra fancy things in there, such as supporting SCSS or LESS, turning off the current theme stylesheet, and overriding default WordPress image sizes. Now that WordPress has supported custom CSS for a long while, we are removing the redundancy!

You can find more information regarding this particular deprecation notice here:
https://jetpack.com/support/custom-css/

Hopefully this clarifies things, please let us know if you have further questions about this!

I totally empathize with that @nonfascist!

The good news is that in most cases, Jetpack and WordPress will have already taken care of moving any custom styles over for you, and simply turning off the feature as you have just done is all that needs to be done ?? ??

I will provide more technical mumbo jumbo below, just for good measure:

You should be able to see if you are using any custom CSS by visiting this page on your site:
/wp-admin/customize.php?autofocus[section]=custom_css

If there is any content in the text box on the bottom left of the screen, that is your custom CSS which has already been moved over for you. If there is no content here, or there is CSS, then we are good to go!

The cases that need more technical intervention (i.e. “converting to CSS”) is when the custom styles were written with a different styling language such as LESS or SCSS. The deprecated Jetpack feature included support for writing CSS with different languages, which WordPress does not include.

If you do have content in this box, and are unsure if you need to take any additional steps, feel free to share the styles here and I can let you know if they need conversion/convert them to CSS on your behalf.

Cheers!

Hello there @nonfascist

You can find more information regarding this particular deprecation notice here:
https://jetpack.com/support/custom-css/

In short, starting version 13.7 (scheduled for August 2024), Jetpack will no longer support the Custom CSS feature.

1. If your site has WP_DEBUG enabled, deprecated features and warnings like these are printed out when the page loads. For a production site, it is recommended to have WP_DEBUG disabled to prevent system debug messages from being shown to your users. More information about how to control this value can be found here: https://jetpack.com/blog/wp-config-php/

I would recommend ensuring WP_DEBUG is false when in production, and true when in development.

2. You can check if your site is using Jetpack’s Custom CSS feature by visiting Jetpack → Settings → Writing in your site’s dashboard. Scroll down to the Theme Enhancements section and review the Enhance CSS customization panel option.

If the custom CSS feature is enabled, I would recommend turning it off to remove the deprecation warning and have your site ready for the eventual update 13.7 which will remove the feature. You can move any custom styles to the Appearance → Customize panel in your WordPress admin dashboard (if you have used SCSS or LESS to write these styles, you will need to convert them to CSS before moving them over).

I hope this information is useful, and please let me know if you have additional questions regarding this issue, or anything else Jetpack!

Hey there @mozzie156! I’m sorry to hear your site is having troubles with the Brute Force Attack Protection feature, and would be happy to help out here.

If your Jetpack is connected to a WordPress.com account, you can remotely disable the brute force protection feature here: https://wordpress.com/settings/security

Otherwise, I would recommend opening a support ticket with Jetpack, and we can remotely disable the brute force protection module on your behalf.

Finally, we have some troubleshooting information for the feature with instructions on how to disable the feature completely, or to allow your IP address to bypass the math requirement while still protecting your site from brute force attacks.

Hopefully this information is useful – please let me know if you do open a support ticket, and I will ensure that it is taken care of right away!

Hey there PenTwist, I’m very sorry to hear that Protect isn’t functioning as you are expecting. May I ask if you are using the free or upgraded version of the plugin?

Currently, the free version of Jetpack Protect provides reporting on known vulnerabilities found in the themes and plugins currently installed on your site, brute force login attack protection, and a manual IP block and allow list.

The upgraded version of Protect includes a Web Application Firewall (WAF) that inspects every request against our advanced security rules and blocks bad actors, as well as advanced line-by-line malware scanning for your site. Protect does not include rate limiting or DDOS attack protection at this time.

Please let us know if you have any other questions or feedback about the plugin!

Hello Kevin,

I’ve been working to try and reproduce this behavior with the latest versions of MainWP Dashboard/Child, Jetpack Protect, and WooCommerce without any luck so far. I see that your site is back up online with Jetpack disconnected, were you able to resolve the issue on your end?

Hello Kevin, I’m very sorry to hear that Protect is not deactivating properly and would be very happy to help you get things back up and running!

1. Do you have access to the PHP error logs on your website? This would give us a clear indication of where the problem is occurring and how to go about fixing it.
2. Were you using Jetpack Protect’s Firewall feature, and if so, did you at any point configure it to run in “standalone” mode? This would have required some technical actions by yourself or your web host. If this was the case, it is possible your server is still configured to be running scripts from Protect, and may cause issues if the plugin was removed:

Enhanced protection
Learn how you can execute Jetpack Firewall before WordPress initializes. This mode offers the most protection.

To ensure the firewall can best protect your site, please update: auto_prepend_file PHP directive to point to wp-content/jetpack-waf/bootstrap.php Typically this is set either in an .htaccess file or in the global PHP configuration; contact your host for further assistance.

Don’t forget to undo this action when Firewall is turned off, or when you uninstall Jetpack.

Please let me know about the above, and I will continue to investigate this in the meantime!

• This reply was modified 1 year, 4 months ago by njweller. Reason: Added more information