fbf / laravel-blog Goto Github PK

i followed the installation guide:
. i installed a new laravel package (4.2)
. i added "fbf/laravel-blog": "dev-master" at the end of the composer.json file
. I launched composer update command (without error messages)
. i added 'Fbf\LaravelBlog\LaravelBlogServiceProvider' into app/config/app.php (into providers array)
. i launched "php artisan migrate --package=fbf/laravel-blog", but the output it's:

PHP Fatal error: Class 'Fbf\LaravelBlog\LaravelBlogServiceProvider' not found in /var/www/mypro/bootstrap/compiled.php on line 4415
{"error":{"type":"Symfony\Component\Debug\Exception\FatalErrorException","message":"Class 'Fbf\LaravelBlog\LaravelBlogServiceProvider' not found","file":"/var/www/mypro/bootstrap/compiled.php","line":4415}}

where i wrong?

Composer update fails on:

• fbf/laravel-blog dev-master requires illuminate/support 4.0.x -> satisfiable by laravel/framework[4.0.x-dev, v4.0.0, v4.0.0-BETA2, v4.0.0-BETA3, v4.0.0-BETA4, v4.0.1, v4.0.10, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9], illuminate/support[4.0.x-dev, v4.0.0, v4.0.0-BETA2, v4.0.0-BETA3, v4.0.0-BETA4, v4.0.1, v4.0.10, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9].

In the commit 462d6b3 a new parameter is added to the function getImage() in src/models/Post.php. This parameter has the default of [] which is the shorthand for an array as introduced in PHP 5.4.

Since Laravel < 4.2 is designed for PHP 5.3 upwards this means that in environments where your package is being used on PHP 5.3 the user is forced to use version 0.7.

Since this is such a small detail I have done a pull request changing the shorthand array into array(). Though I also understand that maybe you want to force users to update, in which case it might be good to change the composer.json to require PHP 5.4 for versions above 0.7.

I hope this is detailed enough, first pull request :D

Or how are you sorting the posts?

I can't save new posts with Frozennode Administrator. I used the config file as found here.

When I click save I get the following error: Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://localhost/admin/posts/0/save.

I think there is a problem with the config-file but I can't find out what...

I cannot make TC/IP connections to Postgres (using postgres.app) server, even after configuring pg_hba and pgpostgres files to listen to different than localhost addresses. Any thoughts? Localhost is on a mac

I can't install the laravel blog package because the rss package has been updated. I think it needs changing to rss-l4

The current migration directly affects the database. This is problematic when someone attempts to replicate the environment on a different server, as that migration is not part of the migration history on disk. i.e. When somebody attempts to set up the database on a freshly checked-out copy of a project with php artisan migrate, this migration will be missing. What would be much better is if the artisan command in this package were to generate a migration that could then be committed to source control.

Thanks!

Hey,

i`m totally new to lavarel and i tried to install your blog.
But i get some errors with artisan

And in the Frontend i get this error:

Illuminate \ Database \ QueryException
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'lavarel.fbf_blog_posts' doesn't exist (SQL: select count(*) as aggregate from fbf_blog_posts where fbf_blog_posts.status = APPROVED and fbf_blog_posts.published_date <= 2014-04-01 08:19:25)

What do i wrong ?

Hi,
Would it be possible to mark this with a release? It makes it easer to use in production as we can fix it to a release rather then constantly using dev-master which isn't best practice.

I'd suggest starting at 0.1.0 for this release.

Thanks.

when i make an update on a post on the fronzennode/adminisrator backend you made a module it does not work, only work when you make a new post, the update does not work

It appears the /blog url is causing a too many redirect loop issue. If I keep accessing the /blog it will switch the url between "/blog/" and "/blog".

The actual posts are showing up fine though.

Has anybody else had this issue? I have tried re-installing and that did not work.

First of all, thanks very much for this packagae - it has saved a lot of time, even though I've done a little modification for my own requirements.

Speaking of which, I've noticed that there isn't a configuration file for the messages that get used in the views, for example:

{{ trans('laravel-blog::messages.share.facebook') }}

After publishing the configration to my project, I've tried creating a configuration file called messages.php under the package's config directory, with the following contents:

return array(
    'adjacent' => array (
        'prev_link_text' => '< :title',
        'next_link_text' => '> :title'
    ),
    'share' => array (
        'twitter' => 'Yo!'
    )
);

However this doesn't change the output at all. Have I done something wrong?

Year not a known function in SQLite, this won't work with projects that rely on SQLite either for testing or in production.

I have a fresh 4.2 install and required your package in my composer.json and did a composer update, see below for what I got back.

/Applications/MAMP/htdocs/trafficblog: composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for fbf/laravel-blog dev-master -> satisfiable by fbf/laravel-blog[dev-master].
    - fbf/laravel-blog dev-master requires thujohn/rss dev-master -> no matching package found.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.

Anytime I try to run any command with artisan, I get:

[InvalidArgumentException]
Unsupported driver [laravel]

Any solutions?

For example, in my vendor/fbf/laravel-blog/src/config/views.php, I have:

<?php

/**
 * Configuration options for the built-in views
 */
return array(

    /**
     * Date format for published date, shown on partials.list and partials.details. Should be
     * a valid date() format string, e.g.
     *
     * @type string
     */
    'published_date_format' => 'jS F, Y',

, but yet the blog doesn't seem to be reading and updating. Same thing goes with the header tag, it still reads "My Blog" instead of what I actually set it to.

I'm using the Frozennode Admistrator with the posts module provided. Clicking to make a new post has the new post entry about 20% of the screen width, and the listing of posts the other 80%. I would expect it to be the opposite or the listing of posts omitted.

When I try to access the URL for the RSS feed, the application dies with a "Class 'Fbf\LaravelBlog\Rss' not found" exception.

Looks like Laravel interprets the dot in the URL as a separator for another controller, which is obviously incorrect.

What would be a good solution here?
And is this a problem with Laravel or Laravel-Blog?

Hi everyone,
to add blog functionality to your laravel website, you just need a package. This is compatible with latest version of laravel framework (laravel 8):
https://github.com/vhessam/laravel-blogger

Might need to make a note that some of the queries - since they are raw - don't support Postgres.

Hi guys,

currently i'm trying the administrator package in my Lavaral 4.1 environment (local, OSX, PHP 5.4.4).

I've run the fakeSeeder to get some demo content - okay
The backend it also working.

But even when i try to show the blog post in the frontend, i got an

Symfony \ Component \ HttpKernel \ Exception \ NotFoundHttpException

I've tested it with the following url:
http://localhost:8888/< project-name >/public/index.php/blog/molestias-praesentium

My composer.json looks like

{
    "name": "laravel/laravel",
    "description": "The Laravel Framework.",
    "keywords": ["framework", "laravel"],
    "license": "MIT",
    "require": {
        "laravel/framework": "4.1.*",
        "frozennode/administrator": "dev-master",
        "fbf/laravel-pages": "dev-master",
        "cartalyst/sentry": "2.0.*",
        "fbf/laravel-blog": "dev-master"
    },
    "autoload": {
        "classmap": [
            "app/commands",
            "app/controllers",
            "app/models",
            "app/database/migrations",
            "app/database/seeds",
            "app/tests/TestCase.php"
        ]
    },
    "scripts": {
        "post-install-cmd": [
            "php artisan clear-compiled",
            "php artisan optimize",
            "php artisan asset:publish frozennode/administrator"
        ],
        "post-update-cmd": [
            "php artisan clear-compiled",
            "php artisan optimize",
            "php artisan asset:publish frozennode/administrator"
        ],
        "post-create-project-cmd": [
            "php artisan key:generate"
        ]
    },
    "config": {
        "preferred-install": "dist"
    },
    "minimum-stability": "dev"
}

The log file is the following

[2014-02-04 15:52:12] production.ERROR: exception 'Symfony\Component\HttpKernel\Exception\NotFoundHttpException' in /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:871
Stack trace:
#0 /Applications/MAMP/htdocs/<projectname>/workbench/pseudoagentur/users/vendor/illuminate/support/Illuminate/Support/Facades/Facade.php(208): Illuminate\Foundation\Application->abort(404)
#1 /Applications/MAMP/htdocs/<projectname>/vendor/fbf/laravel-pages/src/controllers/PagesController.php(21): Illuminate\Support\Facades\Facade::__callStatic('abort', Array)
#2 /Applications/MAMP/htdocs/<projectname>/vendor/fbf/laravel-pages/src/controllers/PagesController.php(21): Illuminate\Support\Facades\App::abort(404)
#3 [internal function]: Fbf\LaravelPages\PagesController->view('blog/molestias-...')
#4 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(194): call_user_func_array(Array, Array)
#5 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(93): Illuminate\Routing\Controller->callAction('view', Array)
#6 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(62): Illuminate\Routing\ControllerDispatcher->call(Object(Fbf\LaravelPages\PagesController), Object(Illuminate\Routing\Route), 'view')
#7 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Routing/Router.php(934): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request), 'Fbf\LaravelPage...', 'view')
#8 [internal function]: Illuminate\Routing\Router->Illuminate\Routing\{closure}('blog/molestias-...')
#9 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Routing/Route.php(105): call_user_func_array(Object(Closure), Array)
#10 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Routing/Router.php(1000): Illuminate\Routing\Route->run(Object(Illuminate\Http\Request))
#11 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Routing/Router.php(968): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#12 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(738): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#13 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(708): Illuminate\Foundation\Application->dispatch(Object(Illuminate\Http\Request))
#14 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Http/FrameGuard.php(38): Illuminate\Foundation\Application->handle(Object(Illuminate\Http\Request), 1, true)
#15 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Session/Middleware.php(72): Illuminate\Http\FrameGuard->handle(Object(Illuminate\Http\Request), 1, true)
#16 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Cookie/Queue.php(47): Illuminate\Session\Middleware->handle(Object(Illuminate\Http\Request), 1, true)
#17 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Cookie/Guard.php(51): Illuminate\Cookie\Queue->handle(Object(Illuminate\Http\Request), 1, true)
#18 /Applications/MAMP/htdocs/<projectname>/vendor/stack/builder/src/Stack/StackedHttpKernel.php(23): Illuminate\Cookie\Guard->handle(Object(Illuminate\Http\Request), 1, true)
#19 /Applications/MAMP/htdocs/<projectname>/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(606): Stack\StackedHttpKernel->handle(Object(Illuminate\Http\Request))
#20 /Applications/MAMP/htdocs/<projectname>/public/index.php(49): Illuminate\Foundation\Application->run()
#21 {main} [] []

Hope you can help me.
Thanks!

I get this error when I run php artisan db:seed --class="Fbf\LaravelBlog\PostTableFakeSeeder":

[BadMethodCallException]
Call to undefined method Illuminate\Database\Query\Builder::withTrashed()

I believe this is related to the updated softDelete traits. I am running Laravel ver 4.2.3.

I love how easy it is to integrate into an existing Laravel install, and the simplicity of its use.

Do you have any plans to add Tags, Categories, or the ability to Preview Draft posts? Those are a few things I think that would really round out its functionality.

Hey

Just wondered if you had an plans to support Laravel 5?

Thanks

Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for fbf/laravel-blog dev-master -> satisfiable by fbf
/laravel-blog[dev-master].
- fbf/laravel-blog dev-master requires thujohn/rss-l4 dev-master -> no match
ing package found.

Please check the requirements and how should i fix this.