David Jay

I have since learned that GFWA has not yet been updated for Genesis 2.0

Thanks for the response but I apologize for the inquiry. You beat me to the response

I realized in was my custom post template that was causing the problem. I was using a loop with 1 post so it was pulling the information for the most recent form submission.

I am new to php and custom post types but your plugin is helping a lot.

Thanks again for the response and great plugin.

Dave

I figured this out. Even though I had already created the custom fields, I had to add them in as new while creating the form.

I also prefixed them with “wpcf”. I think I was confused by this post by Yoast that indicates that if the fields are assigned to a group that you don’t need to use the “wpcf”.

I also updated to Gravity Forms v1.6.3.

I figured this out. Not sure exactly what made it work. I may have been a little confused with the description on this post by Yoast that said you don’t have to prefix the custom field name with “wpcf” if you are using a custom field group.

My fields are included in a custom field group but I still need to prefix them with “wpcf”. Even though my custom fields already existed (created in Types) I had to add them as “New” when creating the form.

I also updated to Gravity Forms v1.6.3.

@alchymyth – Thanks so much. That worked.

I have a follow up question if you don’t mind.

Do you know how to show starting default text in the dropdown box (e.g., Select a location)? I am familiar with the show_option_none=YOUR DEFAULT TEXT HERE command used with wp_dropdown_categories but can’t get it work with get_terms_dropdown.

Actually, the entire code I used in the PasteBin works perfectly. For one taxonomy.

The problem is when I try to add another dropdown (using the same code) for a different taxonomy. I am not trying to search based on multiple taxonomies, just offer readers the ability to search different ways – one of a few taxonomies.

My apologies for the rules violation. The deleted code from above is at https://pastebin.com/wpPbPGEQ

I fixed it. At least so far. Here is what I did.

I deactivated plugins (all but a core ones) one-by-one but the issue still persisted. I then un-installed MU sitewide tags and re-installed it and I was able to publish blog posts just fine. I have since re-activated most of the plugins without a problem. So it seems best to activate Sitewide Tags before activated other plugins if you have the choice.

I will update this if the problem occurs again after installing another plugin.

My situation was a little different but I wanted to post it in case others have the same problem.

After activating the No Category Base plug-in when I went to some blog posts I was shown the category page.

After deactivating the plug-in I got a 404 error when I went to those blog posts.

Turns out I had blog posts with the same URL as the new (i.e., without the /category/) category pages.

I changed the slug on the affected categories and everything was fine. Maybe this warning is there somewhere and I didn’t read all the fine print, but if not perhaps it should be added as a warning.

It is working now.

Thanks for all your help.

Correct, I have page titled blog which is assigned as the posts page.

Thanks for the suggestions. One problem solved, one left.

I did have a directory called blog on my server. After deleted it I no longer get the error message but no posts show up on the page.

I activated the static home page but that did not help.