trouble activating listing items
This topic contains 13 replies, has 4 voices, and was last updated by Paolo 8 years, 6 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket-
AuthorPosts
-
October 11, 2016 at 12:40 am #280929
it seems im missing out on something to “publish” the items. my install at http://intouchdev.wpengine.com/ is working ok for the demo items supplied, but none of the user-supplied ones seems to be correctly “publishing” on the frontend. My items are set to be created by the user and saved into “draft” mode. I’ve went into the admin and manually activated them by using the regular wordpress article “publish” technique (in the item edit page on the right sidebar – publish button )
the items still dont appear in the listings.
when I try to preview them from the admin it results in a 404 page.
can you let me know what is setup wrong, thanks for your support.
I have a debug account ready for you if needed
October 11, 2016 at 7:21 am #281068Hi Hugues,
Do you think you can share WP temp admin access to your site so we can take a better look? You can post the details here using the private reply option below.
Thanks!
October 13, 2016 at 2:13 pm #283083This reply has been marked as private.October 13, 2016 at 6:58 pm #283336Hi,
I just had a look and what seems to be the problem is that there are plenty of mandatory fields that are empty in each of the listings.
These mandatory custom fields are visible in the back end and not in the front end…
Hope this helps.
Let us know,
Thanks
p.s. very nice website… 🙂
October 13, 2016 at 9:20 pm #283435hello – those mandatory fields are also not filled up in the demo content supplied, but they do publish correctly.
please take the time to figure out the real reason why they dont publish –
is there a condition in the backend tom prevent publishing of items with required fields missing – and if so – where can I override this?
my client has a presentation in a few days, we really need those user-supplied t=items to publish asap… thanks
October 13, 2016 at 11:09 pm #283488if its of any help – even hitting the “preview” link from the admin renders a 404 error page, and that with the post published, visible, and not private… you can try with item “test”
October 13, 2016 at 11:13 pm #283489Hi,
the demo content supplied is supplied published with or without you creating the custom fields.
Please try to put a generic value in all of those fields, or make them non mandatory and you will see that the listings will get published.
After all, that is the logic behind mandatory fields.
Thanks
October 13, 2016 at 11:16 pm #283491did so right now with the “test item” – doesnt change the fact its not showing in this page http://intouchdev.wpengine.com/c/alimentation/
October 13, 2016 at 11:22 pm #283522I see that listing set as private and you are currently in modifying it. Did you try setting it as published instead of private?
Let me know if you logged out of it so I can check.
Thanks
October 13, 2016 at 11:44 pm #283540im out now, you can change anything in this article
October 14, 2016 at 1:39 pm #283880any progress? sorry to pressure you – my client needs this to work this weekend, absolutely…
October 14, 2016 at 2:44 pm #283940This reply has been marked as private.October 15, 2016 at 2:54 pm #284841ive added the js code that hides the “conditionally required” infos, and now the item publishes fine…
it would be nice for you guys to officially support conditionally required field… the logic for this isn’t too complicated… just hide the fields with a little js/jquery.
it would really add to the capacities of the signup form to have better field management. ive had to twist the system quite a bit to make it require some confirmation certification # only when those certifications are selected from the dropdown.
anyways here is the code if you have any use for it!
ive had to put it on the front and backend JS./* empreintes contextual fields */ $('select#geodir_empreinte').change(function() { $( "select#geodir_empreinte option" ).each(function() { var slug = $(this).val().substr(5); var toShowId = "#geodir_empr_details_"+slug+"_row"; if (this.selected){ $( toShowId ).slideDown('fast'); }else{ $( toShowId ).slideUp('fast'); } }); }); /* certifications contextual fields */ $('select#geodir_certifications').change(function() { $( "select#geodir_certifications option" ).each(function() { var slug = $(this).val().substr(5); slug = slug.replace('-','_'); var toShowId = "#geodir_cert_details_"+slug+"_row"; if (this.selected){ $( toShowId ).slideDown('fast'); }else{ $( toShowId ).slideUp('fast'); } }); }); $('select#geodir_empreinte').trigger('change'); $('select#geodir_certifications').trigger('change');
Thanks for your support, its really appreciated
October 15, 2016 at 3:06 pm #284842great thanks for sharing your solution. 🙂
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket