Back to RssFeedster Support

zeropanic
zeropanic

Hello!

I am trying your RSSFeedster plugin. I like how customizable it is, but I'm having an exception when I try to access my feed:

Trying to get property of non-object: /var/www/html/plugins/koderhut/rssfeedster/classes/support/adapters/BlogPostXmlAdapter.php line 51

This line access to user->email and user->full_name.

I'm using October's build 402.

Here is the stack trace:

48 KoderHut\RssFeedster\Classes\Support\Adapters\BlogPostXmlAdapter->getDataValue(…) ~/plugins/koderhut/rssfeedster/classes/view/XmlRenderer.php 89 47 KoderHut\RssFeedster\Classes\View\XmlRenderer->renderData(…) ~/plugins/koderhut/rssfeedster/classes/Feedster.php 136 46 KoderHut\RssFeedster\Classes\Feedster->getFeed() ~/plugins/koderhut/rssfeedster/controllers/Rss.php 29 45 KoderHut\RssFeedster\Controllers\Rss->buildRssFeed()
44 call_user_func_array(…) ~/vendor/laravel/framework/src/Illuminate/Routing/Controller.php 256 43 Illuminate\Routing\Controller->callAction(…) ~/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php 164 42 Illuminate\Routing\ControllerDispatcher->call(…) ~/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php 112 41 Illuminate\Routing\ControllerDispatcher->Illuminate\Routing{closure}(…)
40 call_user_func(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 139 39 Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(…)
38 call_user_func(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 103 37 Illuminate\Pipeline\Pipeline->then(…) ~/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php 114 36 Illuminate\Routing\ControllerDispatcher->callWithinStack(…) ~/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php 69 35 Illuminate\Routing\ControllerDispatcher->dispatch(…) ~/vendor/laravel/framework/src/Illuminate/Routing/Route.php 203 34 Illuminate\Routing\Route->runWithCustomDispatcher(…) ~/vendor/laravel/framework/src/Illuminate/Routing/Route.php 134 33 Illuminate\Routing\Route->run(…) ~/vendor/laravel/framework/src/Illuminate/Routing/Router.php 708 32 Illuminate\Routing\Router->Illuminate\Routing{closure}(…)
31 call_user_func(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 139 30 Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(…)
29 call_user_func(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 103 28 Illuminate\Pipeline\Pipeline->then(…) ~/vendor/laravel/framework/src/Illuminate/Routing/Router.php 710 27 Illuminate\Routing\Router->runRouteWithinStack(…) ~/vendor/laravel/framework/src/Illuminate/Routing/Router.php 675 26 Illuminate\Routing\Router->dispatchToRoute(…) ~/vendor/laravel/framework/src/Illuminate/Routing/Router.php 635 25 Illuminate\Routing\Router->dispatch(…) ~/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php 236 24 Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http{closure}(…)
23 call_user_func(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 139 22 Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(…) ~/vendor/barryvdh/laravel-debugbar/src/Middleware/Debugbar.php 51 21 Barryvdh\Debugbar\Middleware\Debugbar->handle(…)
20 call_user_func_array(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 124 19 Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(…) ~/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php 49 18 Illuminate\View\Middleware\ShareErrorsFromSession->handle(…)
17 call_user_func_array(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 124 16 Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(…) ~/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php 62 15 Illuminate\Session\Middleware\StartSession->handle(…)
14 call_user_func_array(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 124 13 Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(…) ~/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php 37 12 Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(…)
11 call_user_func_array(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 124 10 Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(…) ~/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php 59 9 Illuminate\Cookie\Middleware\EncryptCookies->handle(…)
8 call_user_func_array(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 124 7 Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(…) ~/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php 44 6 Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(…)
5 call_user_func_array(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 124 4 Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(…)
3 call_user_func(…) ~/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php 103 2 Illuminate\Pipeline\Pipeline->then(…) ~/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php 122 1 Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(…) ~/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php 87 0 Illuminate\Foundation\Http\Kernel->handle(…) ~/index.php 44

Thanks in advance!

Last updated

zeropanic
zeropanic

So I found the origin of the problem and it has nothing to do with the plugin. I had not much time yesterday to investigate this issue so I finished my investigation this morning.

So the problem comes from the default blog post created when installing Rainlab.Blog plugin. As this post is created by no-one, the plugin cannot access the author email and full-name.

Kind of stupid problem, could have been avoided with more investigation time!

Sorry for bothering, time to review this nice plugin.

denis.rendler
denis.rendler

Thank you, @zeropanic!

You are right about the issue and I will provide a fix asap.

Thank you very much for your support, Denis Rendler

denis.rendler
denis.rendler

Hi, @zeropanic!

The issue you mentioned was fixed and is awaiting release.

Thanks again for letting me know.

1-4 of 4