search

BabDev / Podcast-Manager

Podcast Manager is a suite of extensions allowing users to host and manage a podcast feed from their Joomla! site.
http://www.babdev.com/extensions/podcast-manager
40 stars 16 forks source link

PHP "Strict Standards" errors in Admin view #209

Closed njbair closed 9 years ago

njbair commented 9 years ago

I'm running a fully up-to-date Joomla site with the latest Podcast Manager. I see these errors in the podcast edit view:

Strict Standards: Declaration of PodcastManagerModelPodcast::prepareTable() should be compatible with JModelAdmin::prepareTable($table) in [...]/administrator/components/com_podcastmanager/models/podcast.php on line 27

Strict Standards: Declaration of PodcastManagerTablePodcast::_getAssetParentId() should be compatible with JTable::_getAssetParentId(JTable $table = NULL, $id = NULL) in [...]/administrator/components/com_podcastmanager/tables/podcast.php on line 314

Is this a known bug?

mbabker commented 9 years ago

Yes. Because the code supports Joomla 2.5 and 3.x, there are a few places where there are messages like this displayed because of changes between the two versions. Nothing is broken.

On Sunday, August 16, 2015, Nick Bair notifications@github.com wrote:

I'm running a fully up-to-date Joomla site with the latest Podcast Manager. I see these errors in the podcast edit view:

Strict Standards: Declaration of PodcastManagerModelPodcast::prepareTable() should be compatible with JModelAdmin::prepareTable($table) in _[...]/administrator/components/compodcastmanager/models/podcast.php on line 27

Strict Standards: Declaration of PodcastManagerTablePodcast::_getAssetParentId() should be compatible with JTable::getAssetParentId(JTable $table = NULL, $id = NULL) in [...]/administrator/components/compodcastmanager/tables/podcast.php on line 314

Is this a known bug?

— Reply to this email directly or view it on GitHub https://github.com/BabDev/Podcast-Manager/issues/209.

njbair commented 9 years ago

Thanks. Glad to know nothing's broken. I guess those errors won't even show up in production with display_errors turned off.