mudguts

Dear Andrew
I was answering How do I join? on https://make.www.ads-software.com/training/getting-started/: Fill out our contact form and we will get back to you to help you identify specific tasks.
Could you please tell me how I can contact the www.ads-software.com Training Team, or whoever does make ‘Slack requests’.
Thank you

Hmm, not very helpful. I guess I can forget about joining the meeting on Thursday.

Yes, it’s the same

Me too, sent request 10 hours ago (make.www.ads-software.com/chat/ said it would take just a few minutes). Didn’t notice anything about an alternative email address on that page either.
No reply so far, not in inbox, not in trash, not in spam folder. Any idea how long we might have to sit tight?

Yes, I did and it works ??
I found the absolute path by looking closer at the error message I received previously when I included a protocol prefix in the path (ftp://home/). It turned out to be a Plesk platform, so:
/var/www/vhosts/domain.com/etc/php-errors.log does the trick.
Thanks again, now to start further experimenting with the help of the widget.

I’ve made another attempt and now what I get in the PHP Error Log box in the Dashboard is simply: The log file is empty. – nothing more. Could that now be correct? If so, I’m much obliged to you.

Thanks, Janis, but telling us to add ‘/full/path/to/php-errors.log’ or ‘/home/path/logs/php-errors.log’ is confusing for the nonprofessional. Better would be to give a concrete example.
If I right-click on the empty file I’ve created called ‘php-errors.log’ (writable (664) and in any directory) using my FTP client and choose, for example, ‘Copy Path’, I get ‘ftp://’ at the beginning. That looks odd and sure enough if I include it, I get, for example, ‘The log file ftp://mydomain.de//logs/php-errors.log does not exist or is inaccessible. If I add ‘home’ to the beginning: ‘ftp://home/mydomain.de//logs/php-errors.log’, I actually do get an error message which starts: Warning: is_readable(): php_network_getaddresses: getaddrinfo failed:. But below the message it still says that the file doesn’t exist or is inaccessible. If I get rid of ‘ftp://’ or replace it with ‘full’, it tells me the same thing. But when I put ‘home’ in front: ‘/home/mydomain.de//logs/php-error.log’, it says that the error log filename is not set, plus the usual instructions.

I would like to have error logs on my testing site because I’m having compatibility problems with a plugin that is essential and it would be helpful for the developers of the plugin if they could see an error log output.

Do you have any suggestions? What other information would you need from me?

Thanks for trying, btw

Before risking it again on GoDdady’s server I’ll test it out on another server I’ve got access to (not GD) and then get back to you. It just might take some time to copy everything to it. I could probably get to error logs there too.
Let you know

Unfortunately, I don’t have access to the error log files, GoDaddy only holds them for seven days.

Here’s the URL: kevinstevens.net

And here’s a list of the other plugins I’m employing:
Black Studio TinyMCE Widget
Duplicate Post
Page Builder by SiteOrigin
Post Edit Toolbar
TinyMCE Advanced
WP-Optimize
WYSIWYG Widgets / Widget Blocks

Thanks for your suggestions.
I posted here because I got no reply from https://jetpack.me/contact-support/ which I contacted first.
Specifically, I was using Jetpack 3.6.1 with WP 4.3 and had activated the ‘Extra Sidebar Widgets’ and ‘Widget Visibility’ features and everything was hunky-dory.
I was away from the site for a few weeks but when I returned I was prompted to update to the latest version of WP and to update a number of plugins too, including Jetpack. Without much ado – I did, however, back everything up first – I updated everything in one go. Result: blank page or some kind of generic error message.
I reinstalled WP 4.3 and got things up and running again but ‘Widget Visibilty’ wasn’t working. After replacing the Jetpack folder with the older version I had the functionality back. Finally, I updated WP to 4.3.1 again and everything worked and is still working. But dare I update Jetpack to 3.7?
Could version 3.7 have a compatibilty issue with other plugins? Version 3.6.1 doesn’t. Are you recommending I recreate the problem so you can have a look at it? It took ages to replace the Jetpack folder, by the way! Would it make any sense to supply the URL when there isn’t a problem? The site must be online and functioning this coming Thursday, Sept. 24.
Please advise.

Version 3.6.1 was still working fine after upgrading to WP 4.3.1 but Jetpack 3.7 caused everything to break. Is there an easy way to rollback or downgrade to the previous version?