Hi Gulix,
If you disable our plugin are you still seeing the error? I’m not sure that the error is coming from our plugin – but may be coming from your theme, or another function inside of the functions.php file.
Thanks,
Evan
Thread Starter
gulix
(@gulix)
Hi,
if i disable the plugin, the error or warning is not longer there. Until recently everything was without error.
Thanks… Ralf
I am not sure – what theme are you using?
I have not seen the error before.
Thread Starter
gulix
(@gulix)
I’m not entirely sure. Since the theme is a premium theme – I can’t download it and test to see if I can replicate the issue.
I would recommend switching themes and re-testing to help narrow it down.
Thanks,
Evan
Thread Starter
gulix
(@gulix)
Please switch themes to Twenty Sixteen or Twenty Fifteen. Those are tried and true themes, properly coded closely following the WordPress coding standards.
Thank you.
Evan
Ok, now where is that header coming from? That is not the default twenty sixteen header.
Disable all other plugins but ours, and re-test. If the error disappears, turn on your plugins one at a time until you are able to locate the plugin causing the issues.
Thread Starter
gulix
(@gulix)
so now the problem is not there
I am trying to locate the issue but you are not following the steps that I am outlining above. There is clearly a conflict somewhere – probably with one of that theme shops plugins.
Please re-enable timeline express, disable all of your other plugins and switch themes to twenty sixteen.
If you are still getting the error on a fresh install running twenty sixteen, than that means that I can reproduce the issue and should have no problems locating and patching it.
Thank you,
Evan
Thread Starter
gulix
(@gulix)
it is the plugin for the shortcodes at the theme
Thread Starter
gulix
(@gulix)
it is possible to hide the message or not display
Thanks Ralf
Can you check inside of wp_config if the WP_DEBUG constant is set to true?
References:
https://codex.ww.wp.xz.cn/WP_DEBUG
https://getflywheel.com/wordpress-support/how-do-i-turn-on-wp_debug/
Some errors display <b>only</b> when this setting is set to true. Other options are more severe and will display at all times – to let you know there is a problem.
My guess is that that shortcode plugin is attempting to parse our shortcode, and it’s expecting a separate variable than what is being used with our plugin. I’m not sure why it would be parsing out shortcode.
you may want to reach out to that author and ask them why it is affecting all shortcodes on your site – and not just the ones built into the theme/plugin.
Thanks!
Evan
