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
{{ message }}
Repository navigation
Commit 7ea1300
Browse filesBrowse the repository at this point in the historyBrowse files
- This impacts more than just the post in the report. The detail
@@ -273,7 +273,7 @@ Let's start with searching the code base for existing piece of HTML. Using the B
273
273
274
274
We can assume that the date specific information is going to be in some type of template filter or template tag. So let's try searching our codebase for ``left floated six wide column``. This should have two code matches. One of which will have a child element with the text "Read More", and since that doesn't appear in our HTML, we can exclude it. This leaves us with the template ``projects/templates/posts/includes/list_item.html``. From our search result, we can see that the template tag ``{% nice_datetime ... %}`` is rendering the timestamp.
275
275
276
-
If we wanted to try from the other approach, we'd start by looking at ``project/templates/posts/list.html``. We can see a loop over
276
+
If we wanted to try from the other approach, we'd start by looking at ``project/templates/posts/list.html``. We can see a loop over``page``
277
277
to render individual elements for posts on the page, ``{% for post in page %}``.
278
278
This brings us to the template ``projects/templates/posts/includes/list_item.html``. From there, we'd need to compare the rendered HTML to the template to narrow it down to the template tag ``{% nice_datetime ... %}``.
0 commit comments