You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Previous versions of plone /myimage.jpg would result in the image being viewed
Volto no longer works this way.
The major consequence seems to be search crawlers. The sitemap includes these naked urls. They get indexed and often counted as soft 404s or indexed as pages you really don't want visitors to find.
the robots.txt rules also make it very hard to protect these pages from indexing. the standard rules will preventing indexing /view pages for example, which are the same view
To Reproduce
add image. view the url
Expected behavior
I do think the old plone behaviour is better. but maybe there was a reason this was changed?
Screenshots
If applicable, add screenshots to help explain your problem.
Software (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Volto Version [e.g. 8.5.0]
Plone Version [e.g. 5.2.2]
Plone REST API Version [e.g. 7.0.1]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Previous versions of plone /myimage.jpg would result in the image being viewed
Volto no longer works this way.
The major consequence seems to be search crawlers. The sitemap includes these naked urls. They get indexed and often counted as soft 404s or indexed as pages you really don't want visitors to find.
the robots.txt rules also make it very hard to protect these pages from indexing. the standard rules will preventing indexing /view pages for example, which are the same view
To Reproduce
add image. view the url
Expected behavior
I do think the old plone behaviour is better. but maybe there was a reason this was changed?
Screenshots
If applicable, add screenshots to help explain your problem.
Software (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: