J-BusinessDirectory - After latest upgrade - Custom attributes problem

After upgrading to 5.7.3 we have had a lot of problems with our director.  Things were great and we were 24 hours away from launching a new site and then we upgraded and have had to try an figure out solutions to many problems and not getting anywhere very fast.

The main issues now is like two of seven custom attributes are showing and nothing else.  This is on the front end detail page and the back end edit listing page.  The feilds all show under the custom attributes tab on the back end.

Anyone else have this issue after upgrading?  If so, how did you fix it?

Thanks

I think there are some issues currently being worked on. We are in the  process of upgrading too (to Joomla 4), and after upgrading on our test environment noticed a bunch of similar issues:

- Saving a business listing doesn't work (apparently this happens when you have a custom attribute that is mandatory)

- After taking that mandatory requirement off, then trying to save, it would only keep the first option in a multi-option/multi-select field when you have selected multiple options.

I have filed 2 tickets and received a note that they are working on a solution.

That was not so good news though I also in the process to update to Joomla 4 right now but it seems to work for people here?

I wonder how many sites that are running JBD are already on J4. My guess is not many.  We pretty much only use the listing page with custom attributes, search and search results. No events, reviews, prices,... Our listing page page is very customized though.  In the process (still ongoing) of converting this we ran into many places where we had to refactor template code, css stuff and js.  Primarily due to Boostrap 5 in J4.   Very painful, but worth it.

The attribute issues that you experience are not related to J4. They are caused by an inconsistency in the database structure on your website, on the unique index for the business attributes.
There are a lot of J4 websites that are using the JBD without issues.

George, Thanks for finding the issue and providing a solution for it.  Really appreciate it! 

For those interested. We are currently running on 5.1.x in live and had made a 'small' change to the 'value' field in the custom attribute table, which is a varchar(250) increasing it to varchar(1000) so it would allow for more text. That required the index on companyid,attributeid and value to be dropped.

Turns out that was a really bad idea when we did this... While no problem with the old version the recent update impacted the admin functionality, in particular saving.

It'd be nice to get the db structure allow for more than 250 characters when setting up a custom field (text) in the future though. 

Turned out our issue with the custom attributes was very simple to correct.  We didn't have the attributes assined to the correct categories.  Once we added the custom attributes to the categories we wanted them to be seen, they worked fine.