@joseph-benguira Hi Joseph, thank you very much!
I added a title to the modal (which is not mandatory) and it displayed a little 'close' button on the upper-right corner (as well as the modal title of course).
Maybe it would be nice to move it from the title line, since it is not mandatory, to the modal content?
Anyway, many thanks!
Hi Appdrag team 
We have feeback from people thinking that when a modal opens, they can't exit it because there is no "x" / close button.
I know pressing "esc" or clicking outside of it closes it, but I think it would be nice to have a close button at the top right corner for example, for people who are less comfortable with website navigation.
Many thanks!
Hi all!
I am trying to optimize redirects and HSTS and I get the following error on HSTS preload:
Error: HTTP redirects to www first`http://visigo.fr`
(HTTP) should immediately redirect to `https://visigo.fr` (HTTPS) before adding the www subdomain. Right now, the first redirect is to `https://www.visigo.fr`. The extra redirect is required to ensure that any browser which supports HSTS will record the HSTS entry for the top level domain, not just the subdomain.
Is this something that can be fixed on your side? Thanks!
@jbenguira Hi again!
Here you can find another tool that indefinitely looped through our blog posts.
https://www.xml-sitemaps.com/details-visigo.fr-8ebd7a759.html
Our freelancer suggests that there is something in the link creation logic that must be broken.
Could someone investigate this on your side? I can't see anywhere where we could fix that on ours.
This issue has a very negative impact on our SEO performance, so we would really love to see it fixed.
@jbenguira Hi! I changed the link to use the link with httpS and it still did not work, I had an error in the modal:
www.visigo.fr refused to connect.
but the console told me that X-Frame-Options "SAMEORIGIN" in the http headers were causing that.
So I'm not really sure what the best strategy is if we want to use X-Frame-Options, do you have a recommendation?
Because when I removed it from headers, the modal was working perfectly.
Thanks!
@jbenguira the issue was first spotted on Google search console, so I'm guessing there really is an issue somewhere, maybe in our link creation logic...
If I find out more, I'll definitely let you know. Thank you for answering!
If anyone encounters the same issue, please give me a heads up! I'll be happy to discuss it.
@jbenguira Hi again,
So I could definitely not find where the issue comes from, but it still exists because when I create a sitemap, it goes through all pages, adding a '/blog' everytime it's done with all blog pages.
For example, if you use this website: https://www.xml-sitemaps.com/ to create the visigo.fr sitemap, you will see that at some point it starts adding '/blog' to all elements, and then do it again, looping indefinitely.
Hi all!
I'm using a gallery component.
Clicking on a picture in this gallery opens a modal.
This modal contains another page, which is already published.
When I open the preview link, and click on the picture, the modal opens but its content won't load / it won't display anything, and I get this error in the console:
"Mixed Content: The page at 'https://visigo-3fe790.appdrag.site/preview/projets-proposition-2.html?from-preview=1&from=projets-proposition-2×tamp=1641832361546' was loaded over HTTPS, but requested an insecure frame 'http://www.visigo.fr/preview/projets-covea.html'. This request has been blocked; the content must be served over HTTPS."
Do you have any clue where that could be coming from? And how to fix this?
Thank you!
@jbenguira thanks for your reply. I could not reproduce the issue, but I asked our freelancer to see if he can, or if he remembers how it happened. Will update you as soon as I can, thanks!
Hi all!
We hired an SEO expert to work on our website, and he spotted an issue on links.
I saw the issue when he spotted it (maybe 1 or 2 months ago), but when I tried to tackle it, I could not reproduce it again.
The issue was: each time he was clicking on a link, on the blog, the url would get an additional '/blog' in it.
So it resulted in something like 'ourwebsite.com/blog/blog/blog/blog/blog/article-title'
instead of
'ourwebsite.com/blog/article-title'
I would like to know if that was a known issue that has been fixed since we spotted it (meaning everything's fine and I can remove it from our backlog)?
And if not, if anyone has had this issue already? And how to fix it?
Thanks!