I only provide support for my extension, not for Open Graph/Twitter Cards issues in general.
You're not using my extension so you're on your own.
I only provide support for my extension, not for Open Graph/Twitter Cards issues in general.
My mistake. I switched to your extension now and disabled the other one. Still doing the same thing.AbaddonOrmuz wrote: ↑Tue Jul 02, 2019 5:00 pmI only provide support for my extension, not for Open Graph/Twitter Cards issues in general.
You're not using my extension so you're on your own.
Make sure you disabled the option "Local images" in the settings page (ACP > Extensions > SEO Metadata), it's enabled by default.
That did it! Thank you!AbaddonOrmuz wrote: ↑Wed Jul 03, 2019 6:07 pmMake sure you disabled the option "Local images" in the settings page (ACP > Extensions > SEO Metadata), it's enabled by default.
Clear the cache, after that.
This doesn't do any AJAX calls so whatever issue you're having, I highly doubt it's because of this.koraldon wrote: ↑Sat Jul 13, 2019 5:33 am Hi,
I have upgraded from 1.1RC3 to 1.2Beta2, and I have encountered an ajax issue.
I'm using quickreply reloaded, which worked great with 1.1RC3, but now with 1.2Beta2 it doesn't reload the page after sending a new post, but produces an ajax error... it does send the message though.
I really like both of those extensions, and would be great if this can be fixed.
Thanks
I'm aware how that extension works. What I meant was, I doubt the error is exactly "AJAX Error", it should give you a message, and why that exact message is needed? you might ask. Well, with the exact message text one could dig in the code and maybe know why is happening, saying that there's an "ajax error" doesn't help because it's too ambiguous.koraldon wrote: ↑Sat Jul 13, 2019 7:18 pm I will try and explain.
The quickreply reloaded extension loads the page again after you have posted a quick reply, using Ajax.
What happens is that after you send a quick reply, it posts the reply but fails reloading the page, giving an ajax error. Sadly there is no detailed error what occured.
No, once you visit the topic for the first time, the work is already done, so when you reply to a topic this extension already finished its job, at least until you purge the cache, that's why I highly doubt this extension is the cause of the issue you're having.
It doesn't download pictures, it uses the phpBB interface to see attachments, which happens to be also used to download files (attachments). I created a test post, inspect the image URL.Wuppi wrote: ↑Tue Jul 16, 2019 6:04 pm I have a question about the extension - purely technical - no bug or feature request . Today I cleaned up the "Who is online?" - blocked bots, etc. Suddenly I see a GUEST downloading a picture. The guest has the IP of the server => now it became curious. Why does the server download pictures?
False assumption, as I said, that's what phpBB does, I only construct that URL to point to an attachment of the topic.Wuppi wrote: ↑Tue Jul 16, 2019 6:04 pm I called the server owner and asked what exactly the IP downloads: Various pictures.
I then blocked the IP via htaccess ("403/forbidden"). The calls gave now 403 in the log for these ominous picture downloads - but no further visible problems. When he said that only the first image is downloaded, I knew what was responsible. This has to do with your extension.
Well that's intended, you blocked your own server IP.
Another false assumption, it doesn't check if a guest can see attachments, only if the image is readable.
config.php
. Is cache/production
only if you're using the file
driver and you set production
as the container.Because that's how crawlers (Facebook, Twitter, Google, etc) see your website when you share a topic.
It doesn't solve any problem, and that feature is very specific for you, I don't think that's enough for a new feature.Wuppi wrote: ↑Tue Jul 16, 2019 6:04 pm ... ok and now a (small; absolutely no priority) feature request: the call is made by guest without UserAgent. It would be less irritating if the guest has a UserAgent with something like "SEO Metadata-Extension" - that would have saved us (and maybe other admins who are interested in what's going on in the forum *G*) the research time
Hi,jackennils wrote: ↑Mon Aug 19, 2019 4:42 pm I just updated to 1.2.0-beta3 from 1.1.0 and I get this debug info on every topic: