-
Notifications
You must be signed in to change notification settings - Fork 6
Attachment requests fetch from the post endpoint #33
Comments
Should this be shown as a post? |
Sort of like a post. There's a variety of content types (for image, video, audio, documents, etc.), the template should adapt to each. |
Another question: should these attachments be fetched upon click? E.g: the man of steel image has the following HTML
The given HREF (http://localhost:8888/wordpress/tiled-gallery/man-of-steel) is not matching any of the given routes link (referring only to attachments):
and following the idea of #28, wouldn't this affect SEO? Another thing is, this HTML is not generated by us, but instead by Wordpress, so my second question is: how am I supposed to identify what is an attachment or what is not? If I allow the link to do its default behaviour the whole page will be reloaded - which is not our intention. |
Let's table this for now, we will probably have to write our own attachment templates using a consistent URL. |
Requesting a post attachment (for example, http://local.wordpress.dev/2013/03/tiled-gallery/attachment/man-of-steel), causes the application to attempt to
GET /posts/b3:slug:man-of-steel
instead of (the new)GET /media/b3:slug:man-of-steel
.The text was updated successfully, but these errors were encountered: