moody1337

Hey Ahmed,

thanks four getting back. As requested I sent you an e-mail a few minutes ago.

Looking forward to solve the issue with you guys ??

Downgrade is done.

“At the end of the day, we should all remember that we don’t have to upgrade if things are working well.” Are you serious? How can you get new features or important security patches with this in your mind? Of course you always have to update and keep all plugins and the whole system up2date.

And your last sentence makes me think: you are not a developer to this plugin? If so, pls wait with me for an answer from the developers, which are way more in details what has changed between the version – some blind stab around in the dark will not really lead to any good or working solution.

But yes, you are right, they do their best and its not a complaint by me – its more a hint that something isn’t working for me and maybe for others too. The other way could be to not say anything, be disappointed about the behaviour and don’t use the plugin anymore. But I guess thats also not very helpfull … For me its always some kind of symbiosis: the developer developed some cool stuff and the users help to find bugs, have ideas for new features etc.

• This reply was modified 6 years, 10 months ago by moody1337.
• This reply was modified 6 years, 10 months ago by moody1337.

@frenchomatic Of course they are different, based on production and test-stuff. But to be sure there is no plugin-conflict with any other plugin, I disabled every plugin except the AMP-plugin (what is also the reason why the test-page looks a little bit messi).

I also exported the plugin-settings from production and imported it to the test-page. But the speed issue still persists.

Pls leave me a note when you saw it, I will then downgrade to the version I use on production, so you can see, that this one works like charm

• This reply was modified 6 years, 10 months ago by moody1337.
• This reply was modified 6 years, 10 months ago by moody1337.

Alright, understood. First of all: both pages are on the same machine and there is no hoster, because I host it by myself (like “just rent a machine, put pages on it and thats it”). But I found the web-push-thing: the option was enabled in the plugin option – I disabled it and think, the message you saw is gone. But the page is slow as described and thats the thing:

the only difference between both pages is the plugin version. Fast one runs with 0.9.84, the slow one with 0.9.85.3.

• This reply was modified 6 years, 10 months ago by moody1337.

@robbo55 Did you changed something so its working now?

Sorry for my late reply.

Both pages are on the exactly same server, so I’m not sure what you mean with web push, but I think its not important based on the fact that both pages are exactly the same.

Also I’m wondering how you can have a copy without access to my wordpress-backend and the database. If you just grabbed the html – how should this be a proof for something?

Hey Ahmed,

I got a small inspiration today and looked again into the issue. The reason was another plugin, which integrates two divs around the whole content and it did it also for the amp-version of the site. The solution was quite simple: disable this plugin for every URL with a “/amp/” at the end – now the validator is satisfied and I’m too.

Sorry for the little wasting of your time and thank you anyways for any effort!

Hey Ahmed,

basically I have it on https://www.wihel.de/muenzen-vor-einfuehrung-des-euros_71837/amp/ when I activate the navigation in the plugin-settings. But to prevent errors and unindexing by google, I disabled it and enabled it on a test-site.

How is the error about a wrong parent-tag related to the logo and its witdh and height? On my production-site I have the logo configured correctly.

To answer your questions:
1. nope, I don’t customized anything in the templates
2. I configured the following:
2.1. Custom Logo Re-Size enabled
2.2. Resized Method: flexible width
2.3. Rsize Your Logo: 50

Hey Ahmed,

thanks for your quick reply. On my production-site I disabled the navigation as quick fix based on preventing errors currently (its hard to wait until google has indexed everything again correctly). I configured quickly my test-site with my current theme and the plugin, so you can have a look for example at https://test.wihel.de/muenzen-vor-einfuehrung-des-euros_71837/amp/. There the navigation is activated. The example on my production-site production-site is https://www.wihel.de/muenzen-vor-einfuehrung-des-euros/amp/

And again: why is Google fetching correct information from the SAME website by using another tool and wrong information from the SAME website when using SNAP? I tried it also with a third tool, exactly the same behaviour: only posting via SNAP delivers a wrong information.

So in the end: only posting by SNAP creates a problem, any other tool works as expected. The logical outcome: its a problem by the plugin …

You can also try to check the tags on the website https://developers.facebook.com/tools/debug/sharing/?q=https%3A%2F%2Fwww.wihel.de%2Fdan-patlansky-dog-day%2F and https://search.google.com/structured-data/testing-tool/u/0/?hl=de#url=https%3A%2F%2Fwww.wihel.de%2Fdan-patlansky-dog-day%2F -> no problems.

Would be great if we can leave standard answers behind us and look into the problem directly.

I’m not talking about Facebook, but Google+. And as I described, using another tool the description is correct. So why is SNAP not able to fetch it also in a correct way?

Alright, I created a ticket a few seconds ago.

Is there a way where I can send you some credentials, so you can look directly into my backend?

Of course

Thanks for the fast response – now its working again ??