joand

Okay, that’s good news! I must have it wrong (which means it can be fixed!) I actually think I see where I have gone wrong. This is what I have:

/*Set Front Page from Reading Options*/
$front_page = get_page_by_title( 'Home' );
if(isset( $front_page ) && $front_page->ID) {
update_option('show_on_front', 'page');
update_option('page_on_front', $front_page->ID);
}

/*Assign menus*/

function ocdi_after_import_setup() {
	// Menus to assign after import.
	$primary_menu   = get_term_by( 'name', 'Primary Menu', 'nav_menu' );
	$secondary_menu = get_term_by( 'name', 'Secondary Menu', 'nav_menu' );
	set_theme_mod( 'nav_menu_locations', array(
		'primary-menu'   => $primary_menu->term_id,
		'secondary-menu' => $secondary_menu->term_id,
	));
}
add_action( 'pt-ocdi/after_import', 'ocdi_after_import_setup' );

wp_delete_post(1);
wp_delete_post(2);

I should have everything inside of the function ocdi_after_import_setup – is that right?

Hi @capuderg – yes, it works for me now! Thank you so much for all your help with this, and to Amanda who was up most of the night where she lives trying to get this solved. There are quite a few of us who develop for the Divi theme, and I am sure I speak for all of us that we really appreciate your efforts and responsiveness. There are so many variables involved with WordPress, theme, other plugin updates that can cause things to go wrong – it seems like it is a never ending battle to stay ahead of the game.

Joan

I am in the same boat as Michelle and Amanda (we all develop child themes for Divi). FYI when I installed a child theme using OCDI 2.0.1 on my test site before I updated it to WordPress 4.7 it installed properly with the theme settings .dat file. But when I upgraded the site to WP 4.7 and installed the theme, the theme settings did not import properly. So I assume it has something to do with the customizer features added in WP 4.7.

I figured that the lack of response is an answer – it is certainly not supported here anyways! I did go ahead and use the plugin – it still works fine, and I haven’t found anything better to replace it with. I just worry that some future WordPress update might break it – and I am not a programming genius to be able to figure out how to fix it on my own.

Thank you for the reply. All I see on your site is a pdf documentation file, but it does not include information on how to modify the templates, which is the question that was asked here. If this is available can you please provide a link to it.

Is this documentation available yet? I could not find it on your website.

Thank you!

Okay, after investigating this problem further, it seems that may be the tiny-mce editor that is for some reason adding the <pre><code> although why it doesn’t do it when I don’t add taxonomy I don’t know. Anyways, by adding the shortcode in a code module rather than the text editor I can get it to work properly.

That works, thanks! The listing admin still shows the “Extended Details” heading and the Div’s where the fields would go, but I can live with that. Thank you!

But what will I enqueue? As I mentioned, there is no unique ID or class for the Extended Details.

Mappress only loads the javascript files if there is a Mappress map on the page – so I guess the workaround is to use Mappress and not your lat long map generator.

So do you still need the MapPress plugin to use the Lat and Long? I could be wrong, but I don’t think that was explained in your documentation.

Ah, sorry! I guess I was not talking about the same thing after all! I am trying to get rid of it from the admin screen. I did try enqueing an admin style sheet but it did not work – also I am just trying to get rid of the Extended Details and #listing_details_metabox would get rid of the whole details section (Property Details and Extended Details) if it did work.

I would like to get rid of the Extended Details section also. Where would one put an admin stylesheet?

I am having the same problem – I can’t see any place to add the Google API which is required now in order to use Google Maps

Yes, it is (or at least it was) set to Main Menu, and yes it is very strange! Anyways, I created a new menu in the original site, gave it a different name, exported an new xml. Also I changed the default theme in the importing site to 2016 rather than the parent theme (Divi) in case it was doing something strange. So I don’t know which one of these things did the trick, but at least one of them worked and the menu finally imported properly!! (it only took me all day to sort this out…..) Thank you for your support!