identity
Forum Replies Created
-
Posts
-
I was hoping there was a way to actually prevent it versus hiding it.
While something like this probably wouldn’t trip any search engine spam filters, I generally prefer staying away from any appearance of trying to place content on a page that isn’t accessible to humans.
cheers
Excellent, thanks!
cheers
Thanks for checking.
I definitely think it would be worth looking at adding that kind of functionality.
cheers
Thanks guys.
FYI….not sure if it’s an issue, but I was working on this last night and tried uploading with “geodir_custom_field” and it seems to work. Don’t know if that means that it is needed, it takes it with or without, or I may have messed things up….but the data is showing up and the fields show up in the DB.
One little issue I did run into when I accidentally mis-wrote the category name was that it uploaded the data, but places it within “no category” and it breaks the mapping (marker_json field is null, even though the lat/long coordinates uploaded within their fields).
It would be more helpful if it didn’t accept these entries so that the issue could be corrected outside the system instead of hunting and correcting them later.
cheers
Adrian,
This is a bug I reported and will hopefully be fixed.
In the meantime, couple options might be to use/install Firebug or any other extension on your browser or built in component depending on your browser to identify and modify one of the classes in the above link.
The other option might be to change the font size in your browser to as small as you can and see if that exposes the ones below the window frame.
cheers
Great to hear, cheers
Thanks.
And just remembered one more…for the custom fields, do you use the HTML field name as is, or append geodir_ to it.
example:
HTML field name: sample_field
In the CSV, would that be:
a) sample_field
b) geodir_sample_fieldcheers
He-he, haven’t the faintest idea! But if it wasn’t too complicated, thought I might be able to figure it out.
Sounds like I’ll set aside those that I think I’ll have images for and load them when the images are ready.
Any answer on whether multi-select uploads need to account for empty fields?
cheers
wondering if you have follow up info on the multiselect?
Also, a couple other questions…
– do custom fields need to be in any particular order? Also assuming they are added in the CSV to the right of the regular GD columns?
– Since the CSV can only be used to add listings, is there anyway to handle bulk image upload after listings have been entered? Is it possible to do this via phpMyAdmin? I don’t have images yet or in some cases, have them but they aren’t ready, so I don’t know what they would be named, but wondering if it would be possible to:
a) dump the listings via SQL
b) “connect” which websites I have images for
c) name all images accordingly and mass upload them via the WP Media Upload
d) SQL update the tables with the URL to the respective imagesIf you followed all of that, would that be doable or should I hold off on those that I think I’ll have images for and upload once the images are ready?
cheers
Excellent, thanks paolo
No worries. That would be great though if you get a chance…unfortunately that kind of knowledge is still outside my pay grade 😉
Actually seems like an ideal “configuration” setting as I’m sure the desired limit would vary considerably depending on site specifics.
cheers
No worries! Thanks!
cheers
Thanks. Changes in the actions file will potentially get overwritten though with any updates unless they are ported over every time?
cheers
@Simone,
We may be talking about different things. I understand that the same name can’t be used within a CPT, but what about in multiple CPTs?
Example:
I have 10 different CPTs and I’m creating a “Payment Type” field that will be used across all of the CPTs, kind of like the mandatory fields.
If I give it an HTML Variable name: z_payment_types
I’m not seeing any alert….the system allows me to save it with this name on multiple CPTs. The question then is whether this will create any issues? It would be much easier to use the same name instead of z1_payment_types, z2_payment_types, z3_payment_types, etc.
Does that make more sense? I think you were talking about unique names “within” a CPT, not “across” CPTs…the note within GD on being unique was a bit ambiguous to scope.
cheers
Sorry to bump this up, but would like to get a definitive answer on this as I’m ready to upload 7,000+ records. Whether the HTML variable name can be the same across CPT or not will also make a big difference in how quickly I can do this.
cheers
