GeoDirectory multi-select field cannot handle many select options

This topic contains 11 replies, has 3 voices, and was last updated by  Stiofan O’Connor 8 years ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • November 28, 2017 at 6:39 pm #407210

    Stephen Bromham
    Buyer
    Post count: 23

    Hi, there is a signficant limitation in GeoDirectory plugin’s ability to handle lots of multi select items in a field (e.g. a big list of checkbox options required in a listing).

    How can we override this limitation?

    Geodiretory > Place Settings > Custom Fields

    Under ‘Setup New Field’ if you create a ‘Multi Select’ and paste in a few hundred classification headings (e.g. industry classifications – there are plenty out there!) – the plug-in just errors…

    ‘Column change failed. you have too many columns’

    Can you please remove this limitation? Thanks.

    November 28, 2017 at 6:47 pm #407214

    Stephen Bromham
    Buyer
    Post count: 23
    This reply has been marked as private.
    November 28, 2017 at 10:55 pm #407290

    Paolo
    Site Admin
    Post count: 31211

    Hi Steve,

    Developers have been alerted about your concern. As far as I know, GeoDirectory doesn’t impose any limitation.

    If you search in this forum “column change failed. you have too many columns”, you’ll find 2 topics. In the 1st the member tried to insert data via sql and didn’t do it correctly.
    https://wpgeodirectory.com/support/topic/listing-updates-of-custom-fields-not-stored/page/2/#post-207803

    In the other there were DB problems too: https://wpgeodirectory.com/support/topic/column-change-failed-you-may-have-too-many-columns/#post-379696

    If you provide a link to your website, wp admin and phpmyadmin or cpanel credentials, we will look into this.

    Thanks

    November 29, 2017 at 9:05 am #407334

    Stephen Bromham
    Buyer
    Post count: 23
    This reply has been marked as private.
    November 29, 2017 at 10:31 am #407351

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    Hi Steve,

    We place no limitations, this could be two things, either a post or url limitation or it could be a DB limitation.

    The DB limitation is that a user might store all the option so we need to make the field be able to store them all, but to make search filtering fast it can’t be a TEXT field it has to be something like VARCHAR, but having a large VARCHAR uses up space that is limited to the amount of rows you can have.

    There are a few options and i am actually working on this right now, so i’ll try and build them in to the next version.

    Do you plan on using filtering in the search with these options or just using them to display info only?

    Stiofan

    November 29, 2017 at 11:15 am #407357

    Stephen Bromham
    Buyer
    Post count: 23
    This reply has been marked as private.
    November 29, 2017 at 4:46 pm #407457

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    Hi Steve,

    There are things that can be done with large data sets, the input system is just not optimised for it by default, changing the field type to TEXT will help if you are hitting the DB hard limit for example.

    The output in your example seems off but i note you seem to have added a new output section, did you alter the field output also? If not i can take a look at it if you want.

    Thanks,

    Stiofan

    November 29, 2017 at 6:21 pm #407495

    Stephen Bromham
    Buyer
    Post count: 23
    This reply has been marked as private.
    November 29, 2017 at 6:38 pm #407499

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    yes, i mean on the details table, change to TEXT.

    If you have just added a new tab it should be fine, if you want me to take a look at why its being cut off let me know.

    Did you resolve this? https://wpgeodirectory.com/support/topic/split-page-not-found-2/

    Thanks,

    Stiofan

    November 29, 2017 at 7:43 pm #407515

    Stephen Bromham
    Buyer
    Post count: 23

    OK – we’ll change the MySQL field type to TEXT (details table) and see if it fixes the problem with large Multi-Select fields not saving in the back-end and not displaying on the GD place listing front-end. Thanks.

    November 30, 2017 at 12:21 pm #407605

    Stephen Bromham
    Buyer
    Post count: 23

    Hi Stiofan – it worked thank you. Long check-lists in a multi-select field are now feasible.

    November 30, 2017 at 12:46 pm #407609

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    Thanks for letting us know, i’ll add a check to v2 that if its over X characters to change it to TEXT.

    Thanks,

    Stiofan

  • Author
    Posts
Viewing 12 posts - 1 through 12 (of 12 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
20% Discount Offer
Hurry! Get your 20% discount before it expires. Get 20% Discount