getcomit
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] CF7 V.5.2 not working anymoreOk., got it.
The “problem” for CF7 is the deactivation of the REST API for unauthorized users:add_filter( ‘rest_authentication_errors’, function( $access ) {
if( ! is_user_logged_in() ) {
return new WP_Error( ‘rest_API_cannot_access’, __( ‘Only authenticated users can access the REST API.’, ‘disable-json-api’ ), array( ‘status’ => rest_authorization_required_code() ) );
}
return $access;
});The REST API is one more vector for attackers. If in the future will be found a security problem in the REST API, then there will be a lot of fun out there.
Why you are using that? There is no need for a contact form.
This is the first plugin which is running into problems without the REST API.- This reply was modified 5 years, 9 months ago by getcomit.
Forum: Plugins
In reply to: [Contact Form 7] CF7 V.5.2 not working anymoreThemes:
+————+———-+——–+———+
| name | status | update | version |
+————+———-+——–+———+
| 456repair | active | none | 1.4 |
| storefront | inactive | none | 2.5.8 |
+————+———-+——–+———+Plugins:
+———————————————+———-+———–+———+
| name | status | update | version |
+———————————————+———-+———–+———+
| akismet | active | none | 4.1.6 |
| classic-editor | active | none | 1.5 |
| contact-form-7 | active | none | 5.2 |
| cookie-notice | active | none | 1.3.2 |
| ditty-news-ticker | active | none | 2.2.17 |
| ditty-twitter-ticker | inactive | none | 2.1.9 |
| easy-tables-vc | active | none | 1.0.11 |
| envato-market | active | none | 2.0.3 |
| woocommerce-germanized | active | none | 3.1.11 |
| jetpack | active | none | 8.7.1 |
| LayerSlider | active | available | 6.6.2 |
| lpd_456repair_plugins | active | none | 1.0.0 |
| mailchimp-for-woocommerce | active | none | 2.4.3 |
| noenumeration | active | none | 1.0.1 |
| smart-sidebars-slider | active | none | 2.7 |
| Ultimate_VC_Addons | active | available | 3.16.19 |
| woocommerce | active | none | 4.3.1 |
| woocommerce-gateway-paypal-express-checkout | active | none | 2.0.3 |
| woocommerce-services | active | none | 1.23.2 |
| js_composer | active | available | 5.4.4 |
| wp-fastest-cache | active | none | 0.9.0.9 |
| wp-maintenance-mode | active | none | 2.2.4 |
+———————————————+———-+———–+———+Forum: Fixing WordPress
In reply to: Massive problems with WP 5.0.2 & GutenbergAs said this behavior is also on a clean and fresh installation without anything active.
I tested that on different servers with apache 2.4.25 and 2.4.29, with PHP 7.2.13, 7.0.30 and 5.6.39, MariaDB 10.2.19, 10.1.26 and 10.0.34.All with same result: articles cannot be stored.
The only thing what is different to the standard installations:I disabled the REST API globally within my WP rollout scripts which seems to be the root cause of the Gutenberg problem:
./wp-includes/js/dist/vendor/wp-polyfill.min.js:2:29718:
{
“code”: “rest_API_cannot_access”,
“message”: {
“status”: 403
},
“data”: null
}As I changed that and allowed the REST API for authorized users Gutenberg is then working, but it is still slower than the classic-editor.
What is the advantage of using the REST API for editing an article?
There is no need to edit anything from outside.
For me the complete REST API thing is a security risk.