Hi, Clifford.
Thanks for using ScrapeAZon. I have WP_DEBUG enabled in my development environment, but I am unable to reproduce the notice you’re seeing. Can you provide me with a few details about your configuration?
1. What version of the plugin are you using?
2. Are you using a shortcode or the widget?
3. Are you seeing the error in a page, on a post, on the home page, or in the settings?
4. Have you correctly configured ScrapeAZon prior to attempting to use the shortcode?
5. Are you using the responsive style option?
Thanks and let me know.
James
Thanks for the quick reply.
It was on a page that the shortcode was NOT used on (like 404 page). I didn’t try the widget at all, and the shortcode seemed to work just fine.
Yes, the responsive option was on when I saw the WP_DEBUG on my 404 page.
Hi, Clifford.
No problem. I will continue to attempt to reproduce the error. In the meantime, let me know if it’s a recurring thing on non-shortcode pages and the type of content that’s being generated on the page (i.e., is it a WordPress page, a WordPress post, or something else/something custom?).
The line of code indicated by the notice performs a check for the shortcode prior to adding styles for the content. I’m wondering if that check might produce the debug message on content that is neither a WordPress page nor a WordPress post.
Thanks again. I’ll post an update here if I’m able to reproduce the issue.
James
Hi, Clifford.
By way of update, I reproduced the issue and know the cause. The next revision of the plugin will include a fix.
Thanks for using ScrapeAZon and thanks for letting me know about this.
James
Kudos on the good communication and quick responses.
I was just testing it for someone else so don’t even have it installed anymore, but I’m sure all your users will appreciate it!
