Getting PHP errors in EE 2.8.0
wjthomas9 opened this issue · 10 comments
Hello. I just tried your plugin, but it's giving me some PHP errors when I go the publish screen.
A PHP Error was encountered
Severity: Warning
Message: Invalid argument supplied for foreach()
Filename: wb_category_select/ft.wb_category_select.php
Line Number: 239
A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /Users/jonthomas/Sites/continental/site/be7org4ia/codeigniter/system/core/Exceptions.php:170)
Filename: core/Common.php
Line Number: 446
See screenshot: http://cl.ly/image/052J1A1U2C0u
Hmm, the only case where that should appear is if the category group you've chosen on the back end has no categories. I could probably add something in to fix that, but could you check that the chosen group has categories in it?
I think that’s what the problem was. Thanks!
On March 6, 2014 at 10:29:06 AM, Wes Baker (notifications@github.com) wrote:
Hmm, the only case where that should appear is if the category group you've chosen on the back end has no categories. I could probably add something in to fix that, but could you check that the chosen group has categories in it?
—
Reply to this email directly or view it on GitHub.
Great, I'll take a look at adding a safeguard so it just shows an empty drop down.
Great. I appreciate the help. I’m basically using this as a way to tell my entry what it’s Primary category is, and I think the way you have it set up is going to work for that. Also, Solspace’s Primary Category module isn’t working with EE 2.8 yet. So, I was a little bummed when I thought yours wouldn’t work as well. Not a lot of add ons out there for pulling in category data to the publish field.
Thanks again!
On March 6, 2014 at 10:45:44 AM, Wes Baker (notifications@github.com) wrote:
Great, I'll take a look at adding a safeguard so it just shows an empty drop down.
—
Reply to this email directly or view it on GitHub.
How hard would it be to allow a {category_name} or {category_url_title} title to be output in the tag pair instead of {category_id}?
On March 6, 2014 at 10:49:03 AM, Jon Thomas (jon@analyticl.com) wrote:
Great. I appreciate the help. I’m basically using this as a way to tell my entry what it’s Primary category is, and I think the way you have it set up is going to work for that. Also, Solspace’s Primary Category module isn’t working with EE 2.8 yet. So, I was a little bummed when I thought yours wouldn’t work as well. Not a lot of add ons out there for pulling in category data to the publish field.
Thanks again!
On March 6, 2014 at 10:45:44 AM, Wes Baker (notifications@github.com) wrote:
Great, I'll take a look at adding a safeguard so it just shows an empty drop down.
—
Reply to this email directly or view it on GitHub.
Not sure, I can take a look when I get to fixing the small issue you pointed out.
Awesome.
Would be neat if all the category attributes were accessible. For example, with single use output, maybe something like the relationship tag syntax.
{category_select_field_name:category_id}
{category_select_field_name:category_name}
{category_select_field_name:category_url_title}
etc…
And for tag pairs…
{category_select_field_name}
{category_id}
{category_name}
{category_url_title}
etc...
{/category_select_field_name}
I know all that is way easier said than done, and it’s all over my head, so my thoughts with a grain of salt.
I appreciate the support. This little thing saved my project on content admin ease-of-use since Solspace has yet to update their Primary Category plugin.
- Jon
On March 6, 2014 at 3:24:13 PM, Wes Baker (notifications@github.com) wrote:
Not sure, I can take a look when I get to fixing the small issue you pointed out.
—
Reply to this email directly or view it on GitHub.
Give the latest version a shot and see if it does what you'd expect.
Oh wow. Thank you for putting in the time on this. I will check it out right now and get you my feedback.
On March 7, 2014 at 5:12:36 PM, Wes Baker (notifications@github.com) wrote:
Give the latest version a shot and see if it does what you'd expect.
—
Reply to this email directly or view it on GitHub.
It’s perfect! Thank you so much for doing that. That cleaned up my code quite a bit.
On March 7, 2014 at 5:12:36 PM, Wes Baker (notifications@github.com) wrote:
Give the latest version a shot and see if it does what you'd expect.
—
Reply to this email directly or view it on GitHub.