Costum Field in Front end but not visable in Listing?

  • Resolved leogc

    (@leogc)


    5 years, 6 months ago

    Hi there,

    there should be a possibility in the fron end submission for a custom field, with drop down etc. whcih need to be used by the submitter but will not be visable in the listing, somthing for controle etc. so that the admin get to see it bit it will not be visable in the listing after it is published, hope you understand what i mean

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Alessandro Tesoro

    (@alessandrotesoro)

    Hey @leogc

    This has already been requested by a few other people, it’ll be coming after v1.0.0 ??

    Thread Starter leogc

    (@leogc)

    Great to know, did you see my other suggestions in this open treat: “Some suggestions” ? ;o)

    Thread Starter leogc

    (@leogc)

    So just waiting for this feature to see if we can work with it ??

    Plugin Author Alessandro Tesoro

    (@alessandrotesoro)

    Hey @leogc

    This feature that you requested has just been added to the latest update ??

    Thread Starter leogc

    (@leogc)

    Ok great maybe i give a try later the day just s simple question as i mess up with GeoDirectory, would it be possible to import listings from GeoDirectory to posterno? That would help a lot…

    Thread Starter leogc

    (@leogc)

    Ok great maybe i give a try later the day just s simple question as i mess up with GeoDirector, would it be possible to import listings from GeoDirectory to posterno? That would help a lot…

    Plugin Author Alessandro Tesoro

    (@alessandrotesoro)

    Hi @leogc

    Posterno provides a CSV importer and exporter for free. If you’re able to export listing powered by geodirectory to a csv file, you might be able to import them into Posterno.

    Because the 2 plugins obviously store data in a different way. You’d might need to adapt your geodirectory csv to match the structure of the one supported by Posterno.

    My recommendation is, create a sample listing in Posterno and then export it through the built-in exporter so you can see how the csv is structured in Posterno. Then export the listings from geodirectory and check what columns and rows you need to adapt.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Costum Field in Front end but not visable in Listing?’ is closed to new replies.