wardrobecms / core-archived Goto Github PK

Received password reset email.

Link in email brought me to a 404. Note that the period in the email was not part of the link.

Content of email:

To reset your password, complete this form: http://local.sheldonkotyk.com/password/reset/7fce9e81d3daa43fdff4097c6f2387a7dc6f35ef.

http://local.sheldonkotyk.com/password/reset/7fce9e81d3daa43fdff4097c6f2387a7dc6f35ef
404

Database row was created with the correct key.

I get the error when trying to install the core.

http://paste.laravel.com/Mxg

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

Via - ericlbarnes/wardrobe#70

Change single quotes to double quotes for copying right into json
'wardrobe/core': '1.0.*'
"wardrobe/core": "1.0.*"

The title attributes to the content editor buttons are irrelevant and/or missing completely. It would be nice if each button was given a title which is the action of the button. This improves a11y and reduces ambiguity as to what the buttons do.

I am thinking that the current working document for a user could be stored in cache under the key wardrobe::username-curent.

In reality we could just dump the input as a raw Input array? Then have a query

if CachedPost
   populateWithCachedPost
else
   populateWithNull

@ericbarnes what are you thinking from the JS side. You tell me what you want the data to look like and I will try my darndest to make it happen

I think there was a request for this on the beta repo.

I'm thinking to use the same tag as tumblr <!-- more --> and have a button on the toolbar. This would be seen as a HTML comment so there wouldn't be a need for parsing it out of the content.

The question becomes whether we want to store a short attribute in the DB or parse it on runtime?

Shouldn't take but a few lines to implement it either way.

Getting a 404 when clicking on forgot password link.

A configurable way to add auto-routed pages.

Example Theme Structure

index.blade.php
layout.blade.php
pages/
--about.blade.php
--contact.blade.php

/wardrobe/login/remind

Submitted form and I got a fatal exception
http://local.sheldonkotyk.com/wardrobe/login/remind

Symfony \ Component \ Debug \ Exception \ FatalErrorException
Class 'Wardrobe\Core\Controllers\Password' not found

open: /Users/sheldon/Workspace/sheldonkotyk.com/vendor/wardrobe/core/src/Wardrobe/Core/Controllers/LoginController.php
/**
* Send an email to reset your password.
*/
public function remindSend()
{
$credentials = array('email' => Input::get('email'));

    return Password::remind($credentials, function($message, $user)
    {
        $message->subject('Reset your password');

composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)

• Installing intervention/image (1.4.4)
  Downloading: 100%
• Removing wardrobe/core (dev-master 8ec214e)
• Installing wardrobe/core (dev-master 1f7ddde)
  Downloading: 100%

intervention/image suggests installing intervention/imagecache (Caching extension for the Intervention Image library)
Writing lock file
Generating autoload files
Generating optimized class loader

For mass appeal (and even niche appeal), Wardrobe CMS could benefit from having a notification of when Wardrobe/Core or Laravel/Framework are behind in a minor revision.

I am working on a package we should be able to integrate easily to allow for version comparison and manipulation.

From there we can build an API to check against when a user accesses the admin panel.

Is there a built in command to do the recompilation of these two assets?
If I made changes what's the best way to recompile this?

• Post Search
• Post Filtering
• Post Reordering / Sorting

When attempting to view previews of existing posts, previews are empty. Will start digging into this magic of local storage to see if I can't start pub when a preview link is clicked?

I have a couple things I need to change to properly integrate this, namely the table names used in the models and a couple other things across models/views/controllers. Where would I make these changes? If I make it directly in the vendor directory it will get overwritten when I do a composer update.

What makes most sense to me would be to clone the repo and make changes there then I can pull changes and merge them with mine. The question is where would I clone this too?
Workbench directory?

I need to figure out the best way to work around setting the auth connection for applications where there is auth used in other DB connections...

Haven't researched where else this issue occurs, but in PostController::index(), the Config::get() method is not properly retrieving the per_page configuration.

I'm just not understanding why my delete and deleting events are not getting called while created event is! To create and delete the posts I'm doing it from the base UI.

class Post extends BaseModel implements CommentableModelInterface {

    public static function boot() {
        static::created(function($obj) {
               // this gets called on create
        });
        static::deleting(function($obj) {
         // this does not get called on delete
        });
        static::deleted(function($obj) {
         // this does not get called on delete
        });
    }

I tried seeing if it might be a problem with the chainning

changed

Post::where('id', $id)->where('user_id', $user->id)->delete();

to

$post = Post::where('id', $id)->where('user_id', $user->id);
$post->delete();

The problem is still there. Any idea?

If wardrobe is set to not have a prefix, the URL direct for post previews are not working.

It is doubling up /s. i.e. localhost:800//post/preview/20

I did a fresh install and loged in after installing without the remember me function.
The i clicked logout and got the message.

vendor\wardrobe\core\src\Wardrobe\Core\Controllers\LoginController.php
/**
* Log out the user
*/
public function destroy()
{
    $this->auth->logout();
    return Redirect::to('wardrobe/login');
}

Eric Todo - Post view is getting long and rather confusing. It needs to be refactored to simplify everything.

In the documentation it's wardrobe:config when you actually have to run wardrobe:cofig

When i am on the index page like http://localhost/?page=1or loaclhost, i get all posts with Wardrobe::posts().

But if i am on page 2, like http://localhost/?page=2 i won't get any posts back.

I looked into the code and you call active with (in my case) 1 post per page, shouldn't it call all() on the repository?

I installed the cms with the style "blocky" and added a new entry.
Then i called localhost/rss and get this message:

View [themes.default.atom] not found.

It also seems that the different atom files in the themes folder are messed up.

Just wanted to let you know that in php 5.3.13 the return explode()[] gives a 'an expected [' error.

Following the readme, I tried to run config.

So then I run warcrobe:cofig:

And it works. Just a command typo I'm sure.

Main reason, some URI segments are in english.

Currently, Local Storage is being dumped before a confirmation of save is sent.

This usually isn't a problem, but I have had multiple times where either my session timesout or I switch networks while working on an article. Then when I hit post, the local storage dumps and the post is lost.

I can't remember how this is being handled right now, but the dump should probably wait for the return of a promise from the server.

I i am inside a post, i would like to get the next and previous post to show a kind of pagination the the next post.

Wardrobe allows the user to specify the 'theme' he wants to use, this ended up in the need of setting the 'current' theme in various places (Controllers, views), by either calling the Config or using a custom helper function (theme_view).

Laravel View allows us to define a custom namespace, which would result in a much cleaner approach and, as @ericbarnes mentioned in IRC, allow us to introduce cascading theme views in the future.

So, the idea is to declare a 'wardrobe' namespace which would point to the theme the user has choosen. Some examples:

Routes

Route::get('/about', function()
{
    return View::make('wardrobe::about');
});

Route::get('/tags', function()
{
    return View::make('wardrobe::tags');
});

View:

@extends('wardrobe::layout')

@section('title')
  {{ site_title() }}
@stop

@section('content')
    <section class="home">
        @foreach ($posts as $post)
      @include('wardrobe::inc.post')
    @endforeach

    {{ $posts->links() }}
    </section>
@stop

Controller

    public function tag($tag)
    {
        $posts = $this->posts->activeByTag($tag, Config::get('wardrobe.per_page'));

        return View::make('wardrobe::archive', compact('posts', 'tag'));
    }

    public function show($slug)
    {
        $post = $this->posts->findBySlug($slug);

        if ( ! $post)
                    return App::abort(404, 'Page not found');

        return View::make('wardrobe::post', compact('post'));
    }

Hope the explanation is clear enough.

The CONTRIBUTING.md in wardrobecms/wardrobe links to the wrong repository at http://github.com/wardrobe/core instead of http://github.com/wardrobecms/core

Small typo- cofig

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.

Via - ericlbarnes/wardrobe#69

I have config.php file inside my folder theme, with following content:

<?php
    return array(
        'top_link_tags' => array(
            'tutorial'  => 'Tutorial',
            'showcase'  => 'Showcase'
        ),
    );

But calling {{ Config::get('theme.top_link_tags') }} from my layout.blade.php produce nothing.

Why are the theme view files in the public folder? Is it not possible to keep them in the app/view folder? Just wondering for security reasons for the rare case where your view files may have sensitive information or Blade comments in them.

There seems to be a problem with image drag and drop when running on localhost. The image get copied in the folder but the markdown isn't generated. Although it works in production. I'm not sure what could cause this or if this only happens to me but I wanted to point it out.

All the Wardrobe examples I've seen have Wardrobe installed into it's own standalone Laravel installation. Can Wardrobe be easily installed into an existing Laravel installation that already has hundreds of routes and controllers, etc? Is it flexible for this? Or best at leaving standalone?

I have created a new theme so far and wanted to integrate prettify for the codepreview.
In order to do that every <pre><code> needs to be changed to <pre class="prettyprint linenums"><code>.

So i would suggest an option for the theme to do a str_replace or something similar to the parsed content.

This could be done directly in the view but i think that shoul belong somewhere else.

Swift_TransportException
Cannot send message without a sender address

app/config/mail.php was still set as NULL NULL.

I didn't realize that it was mandatory as the instructions looked like this setting was optional.

|--------------------------------------------------------------------------
| Global "From" Address
|--------------------------------------------------------------------------
|
| You may wish for all e-mails sent by your application to be sent from
| the same address. Here, you may specify a name and address that is
| used globally for all e-mails that are sent by your application.
|
*/

I installed the cms with the theme blocky.
If i try to visit the about page i get a 404, so the routes.php is not integrated into the main routes file.

Trying to install wardrobe in an existing laravel application I get this error:

{"error":{"type":"ErrorException","message":"Argument 2 passed to Illuminate\Auth\Guard::__construct() must be an instance of Illuminate\Session\Store, instance of Illuminate\Session\SessionManager given, called in /home/ebon/uacs/vendor/wardrobe/core/src/Wardrobe/Core/Facades/Wardrobe.php on line 62 and defined","file":"/home/ebon/uacs/vendor/laravel/framework/src/Illuminate/Auth/Guard.php","line":76}}

(where /home/ebon/uacs is the directory the laravel application is hosted in)

I'm trying to make Wardrobe to use another database.
When I run php artisan wardrobe:migrate it says:
[InvalidArgumentException]
Database [wardrobe] not configured.

wardrobe:migrate

Hello,

I downloaded wardrope to local web server, with url:
http://localhost/wardrope

Then starts the installation process on:
http://localhost/wardrobe/public/install

After I finished I was redirected to:
http://localhost/wardrobe/public/wardrobe/public/wardrobe/login
instead of:
http://localhost/wardrobe/public/wardrobe/login

if you want check the code please, I'm not that good with Laravel yet to do it myself.

Greetings.

RIght now if you click on logout, it will add wardrobe to the url and throw a HTTP not found error.

When working with a separate DB connection, the User Validation fails

Just a small issue, with the config, theres a typo.

on line 15 in wardrobe/core/src/Wardrobe/Core/Console/ConfigCommand.php

protected $name = 'wardrobe:cofig';

should probably be 'config'

Im sorry i cannot make a pr, im very busy atm.

I've taken a brief look at some of the wardrobe source, but cannot see an easy way to disable internal wardrobe authentication. My application already has a sufficient authentication system, and I'd prefer to use that.

Look here: https://github.com/wardrobecms/core/blob/master/src/Wardrobe/Core/Controllers/LoginController.php#L63

It hardcodes the route as wardrobe/login instead of calling on the prefix value set in /app/config/packages/wardrobe/core/routes.php. I changed my prefix from wardrobe to admin and that is how I came across this bug.

I thought maybe I could just change it to

...(Config::get('core::routes.admin_group_rules') . '/login');

But that doesn't work I guess since you are trying to call a config value from within the package source. I'm not sure how to fix this to make it dynamically use the prefix value.

After you publish a post, the status automatically changes to draft. I discovered this after opening a post and making multiple edits, saving each time.

To recreate:
Create a new post
Add content
Hit publish (notice the button changes to 'save' instead of 'publish')
View live article in a new tab.
Edit the content
Hit save.
Refresh article tab, article is no longer live.

I guess the assumed functionality would be to maintain the current status upon each save.