ericlbarnes / wardrobe Goto Github PK

Currently you have to parse the markdown for a post. While this isn't too bad, this puts more logic in the view than is necessary. I was thinking that the post model add a body attribute or something similar which would just be a markdown parsed version of the content so {{ md($post->body) }} would just become {{ $post->body }}

Right now, posts that are not yet published are visible to users. Even though the publish date has not arrived, I have pre-composed posts showing in my tag archives and they are visible via their slug.

When I publish a post and go back to edit it, I can save the post but not publish it. The post turns into a draft, thereby disappearing from the site. I couldn't find a button or something to change the status to published.

The slug library needs to support arabic and other locales.

Here are a few I found that may be more flexible:
https://github.com/bengourley/slugg
https://github.com/diegok/slugit-jquery

Open to options if anyone has any recommendations.

Not entirely sure if it's just me who does something wrong, but all the urls on links, buttons and assets is relative to the root. That makes it quite hard to install this in a subfolder, fx www.mysite.com/blog/ :(

In the html stuff I could put in {{ url('path/to/stuff') }} where needed, but I have no idea how to fix it in the backbone part, so I couldn't get it to work with posting new articles :/

Found myself leaving two windows open, because I didn't have an easy way to get back.

Not a blocker, but a small UX improvement.

When you have multiple authors the author select list isn't populating with the current logged in user.

Account currently exists in the admin, but it would be nice to be able to modify the Wardobe config settings from a GUI.

Allow a simple interface to be used in blade to include template css and js files. This is easily done by creating a child of the Laravel HTML Builder that just passes the path through the theme_path helper before passing this on to the traditional HTMLBuilder parent.

This removes logic from the view {{ theme_path('css/style.css') }} inside of a large link tag then just becomes HTML::style('css/style.css'). A different thought would be to create a Theme helper class that would allow syntax like Theme::style('css/style.css') this may be a bit more maintainable as it would still allow Laravel devs to use the HTML facade per usual while giving them a designer friendly API for themes!

I get a 'an expected [' error on the getShortAttributes method in php 5.3.13

It is the explode()[] that is causeing the problem.

I had to rewrite the function

Hovering over toolbar icons there's garbage text in the tooltips.

I need to work on an easier upgrade routine.

I don't actually have an issue, I just wanted to say how awesome this looks! I will be trying it when I get the chance :)

@ericbarnes just something to keep an eye on. But I basically updated everything, repo, back-end and front-end, reran grunt, and served the site and everything looks fine but it appeared to break the editor for new and editing posts.

Didn't have much time to look into it, time to make dinner. :)

Essentially, I would like to see an alternative install process instead of site.com/install since PagodaBox doesn't support install files (being the code is in a read-only environment). The main codebase (aside from app/storage and app/public) can not be modified and makes it difficult to use Wardrobe out of the box on PagodaBox.

Biggest benefit from this, while others could be argued, is that you would be able to do:

composer create-project ericbarnes/wardrobe

And be done with installing.

I noticed today that when the app/config/wardrobe.php file has a bad value for per_page it causes an SQL error. I ran into this when I setup my local config files before I ran the install and that did not update the local config file thus leaving a non integer value and causing an SQL error.

Should DbPostRepository()->active() check to make sure the config var is set?

Would be nice to see this feature implemented https://github.com/Rovak/InlineAttachment

When experimenting with this I found the publish date input pop up, and as you can handle written dates 'Next Friday', 'Next Thursday 10am' and also the format of 'MM/DD/YY' I tend to have enter a UK date format as 'DD/MM/YY' say 14/07/13 but this caused the form to error on submission with the object:object

I think a simple commenting system would be a nice addition. If there was interest I might be able to put together a PR to add the basics of the functionality.

I was trying to create a post in admin area but i receive an error message: "The slug field is required". Wen i open the firebug console i see "ReferenceError: event is not defined".

The error happens in Firefox 21.0 for Ubuntu, when i try to create a post in Chrome 27 runs perfectly.

wardrobe does not delete or update the posts?

There is no problem while inserting new post.

I have the latest version of wardrobe.

What may be the problem?

Thanks.

I will help out with this some, but the markdown isn't being parsed at all into the RSS feed output. This led to a bit of a messy jumble of ## and random numbers. I'm pretty sure this can be fixed with a quick parsing since you are sending the data as html. I will look at it before work tomorrow and likely send a pull request in!

When in the set up screen 'localhost/wardrobe/public/install' and then we press the 'Install Database & Continue' i am given a write permissions error. After investigation it is related to the InstallController@postIndex in whcih it has the following code:

    Artisan::call('key:generate', array('--env' => App::environment()));

Now this obviously want to set a key but as the app.php file is protect its causing the issue, to temporary resolve this i simple commented this out and i managed to get to the next couple of stages.

Before doing this it seems that it is giving it a key automatically, but a closer look is also before running composer install the key is already set and the two versions i have both have the same key - itGxWARLoFR3FxpwAb1ksNlOFhVdJvF0

So is there a need for the Artisan::call call within the controller?

Once this is completed and i get to the application set up, i enter a site name, theme and number of posts per page etc then press enter but then are greeted with another file permission issue.

This time this is to do with the config/wardrobe.php page as it seems its trying to write the form results to this file within the setWardrobeConfig() in particular the File::get($path), but as this file (wardrobe.php) does not have write permissions it fails.

I tested this and changed the permissions and run it again and had no problems using the application.

When adding/editing it needs the ability to change the post date.

Icons are not displaying in toolbars when hosting from php built-in server:

When a title has the question mark sign in it that will be added to the slug. Hence the url will treat everything from that question mark forward as a get request.

It would be better to remove all the ponctuation from the slug automatic system.

Was thinking about this for a few weeks now but wanted to get some feedback.

My idea was some place in the post page add the ability for key value storage. So for example the first input would be an autocomplete that looks against existing keys then whatever value you want.

Let me see if I can give an example:

[input key] [input value]
<button>Add Another</button>

Something like that just free form. I think this would allow tons of flexibility in adding all kinds of crazy stuff.

In db repository, you call paginate on an empty collection. This seems to have caused the issue. Not sure if you would be able to work around in Wardrobe or it needs to be brought up to @taylorotwell?

Hi!
I was wondering if you'd want to translate it in other languages.
All the documentation and even the app itself front&backend of course.

I could do it in Romanian (native speaker) and in Italian (i live in Florence, Italy since aug 2006 and graduated here too).

What do you think?

The documentation is missing information about setting permissions:

Reference:

https://twitter.com/simon_davies/status/350702940325036032
https://twitter.com/simon_davies/status/350703191106650113

It would be nice to have this for big text posts.

I think it would be ideal to allow image uploading via the content. Basically do it the same way github comments work. You drag and drop the image into the content and it uploads behind the scenes and inserts the markdown image with the correct path.

Hello, I get the following error when trying to write a new blog post:
Error:
Object: object

I think that one of the basic features of a blog should be the ability to comment on posts. I didn't see any reference to it, so I submitted this issue.

add a code icon to the toolbar. (and tab in automatically)
at the bottom it gives a word count (it actually counts characters not words)
It would be nice to have a place to find themes.

Great job though 😄

I have had this idea for a while now and figured I should share it and get feedback before I start on it. It will take a pretty large amount of work to accomplish.

On the posts grid/listing page in admin I have been thinking about changing this to a column type setup like trello/tweetdeck.

With the headings being "Planning", "In Progress", "Scheduled", "Published", etc. then you could quickly visualize old ideas you've had and what you started but never finished.

Ideally columns could be created and removed to suit your preference.

What do you think? Like it or hate it?

It would be great if a config file could be included in the themes folder. This would make it easier to add theme-specific options. Thinking of a more elegant solution to straight up including a php file at the top of the layout file.

Hi,
The blog works just fine but when I try to enter the admin it tells me "View [admin.login] not found.". after some debugging it is looking in the public directory for the view which are not there but in app/views.

what can I do about this? is this a known issue?

Regards, Ronnie

We should have the ability to create new users from the admin and also be able to assign users to posts.

I get an "InvalidArgumentException
View [themes.default.index] not found" when I try to open index after install.
"mysite.com/wardrobe" works fine

[edit]
solved the issue by copying the themes folder from public to views

Hi there. I just tested wardrobe, and discovered some inconvinience with the laravel environment/config.

I had to create the folder app/config/local and copy app.php in there, to get the installer working (otherwise FileNotFound error). I checked your .gitignore, and it seems that you excluded that exact folder. Maybe you can add it to the repo, otherwise this could be a bit frustrating to newbie users.

cheers,
simon

I like to save as I'm writing. I hate the fact that every time I hit save, it takes me back to the Posts page. This is kinda related to #64, since it's necessary to save before previewing. That makes keeping a rhythm pretty difficult, and it's jarring to constantly save, find the post I was working on, click on the post, find my place, and get started again.

Additionally, an "auto-save" feature would be a huge quality-of-life improvement for end users.

I made a Windows virtual host wardrobe.dev and then when i went to the install process i hit install it did this:

File does not exist at path C:\xampp\htdocs\wardrobe\app/config/dev/app.php

then once i added the /dev/app.php i re-ran install and

array_replace_recursive(): Argument #2 is not an array in

protected function mergeEnvironment(array $items, $file)
{
   return array_replace_recursive($items, $this->files->getRequire($file));
}

The fix for me was to add to start/global.php

$env = $app->detectEnvironment(array(

  'local' => array('*.dev'),

));

When doing a fresh install I am getting the following error:

composer install
PHP Fatal error:  include(): Cannot redeclare class symfony\component\process\process in phar:///usr/local/bin/composer/vendor/composer/ClassLoader.php on line 185

Fatal error: include(): Cannot redeclare class symfony\component\process\process in phar:///usr/local/bin/composer/vendor/composer/ClassLoader.php on line 185
zend_mm_heap corrupted

Composer version: d498e73363f8dae5b9984bf84ff2a2ca27240925

Regards

When editing a Post the preview button should show a preview according to the current state of the document, currently it shows the latest published version, so a user needs to click "Publish post" before being able to watch the preview, for me the preview should show my changes before I publish the post, so I'm sure that's the way I want it to look.

I don't know why I am having hard time installing Wardrobe (it must be me doing something wrong)

When I go to /install and hit "Install" button, I get following error:

File does not exist at path /var/www/wardrobe/app/config/production/app.php

After creating the path manually, I get following error:

array_replace_recursive(): Argument #2 is not an array

I haven't had a chance to look at the code yet but I guess the installation should be straightforward as per documentation and what others are saying.

Like I said, it must be something to do with me or my server setup.

Can someone help please?

Ta,
Vishal

It might just be me but even though the post is Active (1) in the DB the posts listings show as Drafts.

Tested with Published and Scheduled posts. Everything else works, looks like it is a display only.

Would be nice to be able to include meta data and an image within a theme package, so that if a user was browsing themes in the admin they could see what it will look like.

Could be in a Laravel style config array.