Hi Simion and Tagdiv team,
We found the issue. It is “nginx” blocking the zip extension to be downloaded automatically or uploaded. It is AWS cloud server. You can make this one as case study and update your customers about the known issues.
Please close this thread as resolved.
Thanks for your time.
Hi Simion,
Please check again. It is not only saying “The plugin does not have a valid header.”.
It is also saying, Download failed. Not Found
Screenshot: https://cl.ly/623b0820364e
We uploaded the correct folder to the WP-Content/Plugins directory. But still we are getting this error. Please check.
But actually When I delete the plugin directory and re-install, it says, following error message.
The plugin does not have a valid header.
Downloading installation package from medlife .com/blog/wp-content/themes/Newspaper/includes/plugins/td-composer.zip?uid=5b7d274c2782b…
Download failed. Not Found
Screenshot: https://cl.ly/623b0820364e
Something is wrong in the downloading the files.
Any update?
Please check.
I’ve tried to update via Theme’s Plugin page as well. But it is saying:
The plugin does not have a valid header.
Screencast: https://cl.ly/2l3g1f0H2q1A
Blog URL: https://www.medlife.com/blog/
Same issue here.
But the issue is not fixed yet.
Sent license details as well.
Since this error is continuously coming, I’m deactivating this ad usage from your theme.
Hi,
Yes. Wherever the ad code is present it shows the error.
I just removed the ad code and tested the error is gone. But If I add any text in ad box, the error is coming again.
Example, I entered “Test” in ad box. Now it shows the same error.
Screenshot: https://cl.ly/paYu
@urbanyvr I know the issue. AMP is very sensitive. It should pass all the Google AMP validation rules. But tagdiv released this plugin very urgently to compete with other themes.
Hello,
If I move tagdiv ad widget from top to bottom the error also moves. Then it clearly shows it is coming from Theme files.
Kindly provide the solution ASAP.
Please respond.
Yes. mbstring Enable settings helped fixing this issue.
