dioscouri / f3-blog Goto Github PK

admin/blog/posts
admin/blog/categories
etc

List of posts by category
List of posts by tag [optional]
List of posts by author [optional]

this means on these pages:

1. author
2. tag
3. category

each blog post's featured image should be clickable. related to #20

it references /~lpolak/tienda/public/asset/

References https://github.com/dioscouri/amritasingh-f3/issues/49

Both the author (via their profile page) and the site admin (via the blog admin's settings) should be able to disable social profile urls

By default, they should not display

class="category-x category-y tag-x tag-y"

comments and social cause fatal errors on the settings object

Some of this code is over complicated. Some of the processing doesn't even need to happen. Let's simplify it.

Lots of blogs support these types of URLs:

/blog/2014/05/04/ ==> list of all blog entries from May 4, 2014
/blog/2014/05/ ==> list of all blog entries from May 2014
/blog/2014/ ==> list of all blog entries from 2014

This can just be a part of the \Blog\Site\Controllers\Home::index method
Remember to add support for pagination on those URLs

the /blog/{year} route shouldn't ever conflict with any of the existing routes because all the other ones are more specific ( /post/{slug}, /category/{path}, etc)

Added via \Blog\Settings

Relates to https://github.com/dioscouri/amritasingh-f3/issues/67

and should lead to the post's page

id="post-ID"
class="post-ID type-X format-Y"

For an out-of-the-box install, let's use a horizontal layout.

"Cars", "Porsche", and "Furniture" should all be clickable so that we can view the category's list of posts

Create a post View is not completely shown. A lot of Category section is not reachable.

/admin/blog/post/create

the tags of the post should display in a simple list below the blog's timestamp.

use /resource/action/id
rather than /resource/id/action

They should largely be the same as the Home view

Blog posts require authors. Right now, when the author doesnt exist, the post is assigned to Raf (line 50, file \Models\Posts.php). We should fix this when we get stable.

Need to figure out why. If it's OK for it to be called there, then need to fix this error that occurs when the safemode user has created a blog post:

Fatal error: Call to a member function fullName() on a non-object in /f3-blog/src/Blog/Models/Posts.php on line 71

Added via option in \Blog\Settings

The major share options are:
FB (done)
Twitter (done)
Google+
Pinterest (done)

The list of categories and tags need to reflect the data in the database

Still needs the same features as admin/views/posts/edit

By default, it should just display a clean blog post, but instead we're getting a bunch of guff. See below.

Often (such as on another project i'm working on), the displayed author for an article will be different from the person who actually created the blog post. They're distinct. So for blog posts, lets add an ->author field to the model.

Leave the metadata.creator field alone -- it should continue to track the person who created the blog. But the ->author field should be used for the front-end display. Add an element to f3-users for selecting a user, and include that element in the f3-blog editing form

Check the f3-assets element for a sample of making an element.

The blog posts and categories need to ensure their indexes