webtent

Thanks for the response, the issue is while testing on our dev site. I tried to duplicate on the live site for you to view and all is working as expected. I’ll continue to look at what could be causing the issue on our dev site.

This is resolved. I came across another post that created another user to fix. I invited another user to the Google account. After verifying the new user in Google, I used the new user to obtain the access code and all worked fine.

Still not able to get this to work with our new account. I’d like to add the Plugin Configuration reports the correct UA account:

[ga_profiles_list] => Array
        (
            [0] => Array
                (
                    [0] => All Web Site Data
                    [1] => 194887202
                    [2] => UA-xxxxxxxxx-1
                    [3] => https://www.domain.com
                    [4] => -14400
                    [5] => America/New_York
                    [6] => 
                )

        )

We are running WordPress 5.2 and the latest version of the plugin GADWP v5.3.8.

Also wanted to note that we have other non-web servers with scripts sending events to the new account after merely changing the UA- ID to post to in the script. We also have several places in the same website as this plugin sending events fine using the new ID as well. I did have to replace the existing Google code in our header file as provided in the GA account gtag, it was a bit different.

I found the setting you referenced in the All in One SEO plugin, but it had no effect. We actually want the title, description, and keywords from that the plugin and not those entered in the Thesis theme. There is a two prong issue, we currently have two sets of meta tags and the theme tags do not reflect what we have entered into the theme head tag settings. I also posted this to the theme forum, just wanted to check if there is a way AIO can disable theme produced title, description and keywords head tags altogether.

Same here, we use GA plugin. Is the purpose of the consent to disable GA logging of the visit if they decline and would we need to disable the plugin as not to have the snippet in more than one place?

I have plenty of other jobs that cycle as expected, but not this one. Wonder if there is a way to reset or see results? Backup works fine.

I need to revisit this again, still not able to edit images. Clearly, if everyone else can edit images and we cannot, there must be something missing on our server. I have set up a vanilla CentOS 7.4 server with all updates running Apache 2.4.6 with PHP 7.2 and installed WordPress 4.9.4 all from scratch. I disabled selinux and opened http, https, ssh and ftp in Firewalld. I am using the Twenty Seventeen theme with only the WP Offload S3 Lite v1.3.2 plugin installed and activated. The allow_url_fopen is on, here is the complete PHP info:

https://wp.webtent.net/info.php

I go to the Media Library and upload an image, then click to Edit Image and rotate. When I save, the error in the Apache error log is:

[Mon Mar 26 10:23:11.742252 2018] [php7:warn] [pid 11843] [client 96.254.71.164:49223] PHP Warning: fopen(https://s3.amazonaws.com/wmnf/wp-test/uploads/2017/12/06224532/Linux-Music-e1522074191942.jpg): failed to open stream: HTTP wrapper does not support writeable connections in /var/www/html/wp-includes/class-wp-image-editor.php on line 407, referer: https://wp.webtent.net/wp-admin/upload.php?item=5&mode=edit

That’s it, very easy to duplicate this issue. If allow_url_open is On, then the issue with this stock set up as I described is preventing the s3 protocol from being registered as suggested? How can images be uploaded successfully to the S3 in that case? Or could someone suggest what I am missing?

I set the max_allowed_packet in the my.cnf file for MariaDB to resolve. The default is very low and by changing to ‘max_allowed_packet=100M’, the issue went away. Good luck!

After some dissecting of the page, I found the issue caused by some document code. I posted here in detail…

https://stackoverflow.com/questions/48214315/console-error-with-certain-browser-detection

It is our development site and it is in the admin area, really don’t want to give access necessary. This can be reproduce with clean WordPress and Woocommerce plugin install.

Same issue here, any insight yet?

The RC1 resolved a similar issue we were having with a role not being able to edit. Is it safe for live site or should wait?

Yes, agreed, especially since we don’t have the issue on the live server. Maybe something to do with HTTP Basic Auth on the dev server, I had one plugin cause an issue with that before. Thanks!

Yes, I did find the error appears when any error in the code, but not an error with the plugin itself. For instance, again this morning working on some unrelated code for the same website and received this error in the debug log. If I disable the plugin, I can now see the actual error in my log causing the problem, which was related to using $this out of context in a plugin I was working on. Basically, every time I have an error in my own code, I get the error above instead of the error causing the problem, very frustrating, I have to keep the plugin deactivated on the dev site to avoid while debugging. So, you believe this only happens because of some other custom code?