Lox
Forum Replies Created
-
Forum: Plugins
In reply to: [Carousel Slider Block for Gutenberg] Source codeHello,
I want to contribute back to this plugin, but it isn’t possible because source code isn’t available.
Can you please make it available ?
Thanks
MariaDB [giep_site]> SELECT * FROM wp_options WHERE option_name LIKE 'siteurl' ; +-----------+-------------+-------------------------+----------+ | option_id | option_name | option_value | autoload | +-----------+-------------+-------------------------+----------+ | 1 | siteurl | https://giep.nc/__/core | yes | +-----------+-------------+-------------------------+----------+ 1 row in set (0.00 sec) MariaDB [giep_site]> SELECT * FROM wp_options WHERE option_name LIKE 'home'; +-----------+-------------+-----------------+----------+ | option_id | option_name | option_value | autoload | +-----------+-------------+-----------------+----------+ | 2 | home | https://giep.nc | yes | +-----------+-------------+-----------------+----------+ 1 row in set (0.01 sec)- This reply was modified 5 years, 8 months ago by Lox.
If it was true, I wouldn’t be able to login and administrate because of automatic redirects.
As I said dev.giep.nc is nowhere to been seen. I searched in all tables, and in all files using
grep.MariaDB [(none)]> use giep_site Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed MariaDB [giep_site]> SELECT * FROM <code>wp_options</code> WHERE <code>option_value</code> LIKE '%dev.giep.nc%'; Empty set (0.02 sec)The question is what is making Jetpack servers reply to a different hostname than the one that requested the activation ? Don’t you have that value stored together with the data that permits to detect duplicated websites ?
Can you try deleting it manually please ?I had the same problem on another website, but as a precaution I just tried to activate Jetpack again and it worked this time.
For another one I lost the jetpack connection the same way and could not activate it anymore. I added “www” and could activate it. Which is weird.
I have tried an extension free, fresh installation of WordPress with the same specific directory layout: activation of Jetpack went smooth so it is unrelated to that specificity.
I already tried it, I even tried deleting manually all wp_options and transients containing “jetpack” in their key name. I have just done it again, the issue is still there.
Prior of that, I resurrected dev.giep.nc with a 301 redirect that keeps request_uri. It doesn’t help.
So it is related to the old staging version (dev.giep.nc) which doesn’t hold any wordpress since a while, the new staging version is staging.giep.nc.
It started like so: after updating to 8.9 Jetpack first told me on the production version that it was a copy of the staging version. Then no way to connect back to JetPack and fix it. But https://giep.nc has a proper SSL certificate.
The string “dev.giep.nc” is nowhere to be found in the database or in any file of giep.nc.
Don’t you have it wrong on your side, why are you connecting to dev.giep.nc the jetpack activation request comes form giep.nc ?
- This reply was modified 5 years, 8 months ago by Lox.
I disabled all extension but jetpack and akismet: same issue
I suspect it is related to having copies of it: one for development, one for staging and one public. What happened following the 8.9 update is that the public website told that it was a copy of staging and since then it is not possible to connect jetpack on all version.
The logs:
192.0.112.85 - - [09/Sep/2020:09:58:59 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 207 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com" 192.0.112.85 - - [09/Sep/2020:09:59:00 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 169 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com" 192.0.118.113 - - [09/Sep/2020:09:59:04 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 207 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com" 192.0.118.113 - - [09/Sep/2020:09:59:05 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 169 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com" 192.0.112.116 - - [09/Sep/2020:09:59:16 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 207 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com" 192.0.112.116 - - [09/Sep/2020:09:59:18 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 169 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com" 192.0.118.208 - - [09/Sep/2020:09:59:21 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 207 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com" 192.0.118.208 - - [09/Sep/2020:09:59:23 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 169 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com"It works with an other website with standard directory layout on same host.
- This reply was modified 5 years, 8 months ago by Lox.
I am the host and we are not blocking XMLRPC: https://giep.nc/__/core/xmlrpc.php
Forum: Fixing WordPress
In reply to: Security fix preventing directory traversal broke my workflowThere is an opened ticket for it
Forum: Fixing WordPress
In reply to: Security fix preventing directory traversal broke my workflowThat would make an absolute path but UPLOAD is used to construct URLS too so it won’t work, it has to be relative.
Forum: Fixing WordPress
In reply to: Security fix preventing directory traversal broke my workflowDamn this code breaks wp-cli …
PHP Fatal error: Uncaught Error: Call to undefined function add_filter() in phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1169) : eval()'d code:77Forum: Fixing WordPress
In reply to: Security fix preventing directory traversal broke my workflowThis works but I am wondering if I may just reproduce the fixed security issue doing this.
/** Sets up WordPress vars and included files. */ require_once( ABSPATH . 'wp-settings.php' ); add_filter( 'upload_dir', function ( $upload_dir ) { $prev_basedir = $upload_dir['basedir']; $upload_dir['basedir'] = realpath( $upload_dir['basedir'] ); $upload_dir['path'] = str_replace( $prev_basedir, $upload_dir['basedir'], $upload_dir['path'] ); return $upload_dir; } );I have the same error in multisite on latest WP, PHP 7.2 and version 6.3.2 of jetpack:
Fatal error: Uncaught Error: Class 'Jetpack_Simple_Payments' not found in /wp-content/plugins/jetpack/modules/widgets/simple-payments.php on line 479This broke the websites. Removing the plugin folder is the only way to have them back. Reinstalling it gives the same error.
- This reply was modified 7 years, 10 months ago by Lox.
On May 13 they said :
We’ve found out that the Websocket console error is only displayed if you are not logged into WordPress.com. If you are, the error will be gone.
We are working on a fix for this but I don’t have an exact ETA on it. However, you can remain logged into WordPress.com and the console error won’t be triggered.
I hope it makes sense. Thank you very much for your understanding and patience. Cheers 🙂
Today the issue still exists.