Overlay has stopped working

Yup, this is a page_manager issue. Merlin removed the overlay support in order to fix some performance problems. There are a couple patches that need to be reviewed in order to get the overlays back in.

Marking this "won't fix" since it's actually ctools' problem and well known.

@Tigeda: I just used the patch from http://drupal.org/node/1396212 (comment #4) and it seems to work well.

Actually it'd be better if you used #1120028: Add caching to page_manager_admin_paths()

add the following to a custom module or theme.php file

function NAME_admin_paths_alter(&$paths) {
  $paths['path goes here'] = TRUE;
  $paths['node/*/addnode'] = TRUE; //example
}

Replace "NAME" with the name of the module or theme

Hope this helps.
J.

CorpX, this didn´t work for me. Created my first custom module though :) I might have done it wrong.

1. Created the .info file
2. Created the .module file
3. Added the following code

function NAME_admin_paths_alter(&$paths) {
  $paths['node/add/nameofcontenttype-1'] = TRUE; 
  $paths['node/add/nameofcontenttype-2'] = TRUE; 

}

Thanks.
J

Really, just apply the patch I posted. This is what it does.

Nice one, thanks. Works like a chocolate/strawberry blended smooooothie!

Looks like this is closed. Blue orange the issue with your code is that you need to replace "NAME" with the name of your custom mod
To over ride that hook.

Example.... your module is named mytweaks.

function mytweaks_admin_paths_alter(&$paths) {
  $paths['node/add/nameofcontenttype-1'] = TRUE; 
  $paths['node/add/nameofcontenttype-2'] = TRUE; 

}

if used in a theme template.php file.....

your theme is named blueorange, then

function blueorange_admin_paths_alter(&$paths) {
  $paths['node/add/nameofcontenttype-1'] = TRUE; 
  $paths['node/add/nameofcontenttype-2'] = TRUE; 

}

Enjoy.

@CorpX

PLEASE stop suggesting this. The patch I linked to make the overlay checkbox work, there's no need to custom set this stuff.

Eclipse

Apologizes, EclipseG. Didn't mean to step on any toes. Awesome work on this project. I'm just hesitant to apply any patch that hasn't been commited to a future release yet. If for any reason it doesn't make the next release and you upgrade, you end up trouble shooting again. Leveraging the hook locally avoids that. The patch works great BTW. Thanks.

Anyhow. Thanks for this contribution. Love the project.

--
J.

Yeah, I understand, but there are tools to prevent that, drush make for example is a great way of organizing the modules and patches you'd like applied to your custom code base going forward. In this way you can document any patches necessary to make your site run how you like. Also, that patch will eventually land in ctool. One way or another.

Eclipse