Page not found for newly created Panels page

Have you created a "variant" for this panel?

Hi guys. Any progress with this one? On a simpler scale I have the same problem. I'm getting "page not found" errors on all new Panel layouts after the first two I created.

I'm still testing the variables but I believe the error started when I chose an Omega panel type for the layout - although before that Drupal also started reporting Fatal Error/not enough memory (often at the point or shortly after trying to create new Panels). My PHP.ini file is already set to 32MB.

A bit more detail: I'm a relative newbee with Drupal (2 years in) and have only just started looking at Panels more thoroughly hence still corss-checking/testing if there's anything in my set-up that could be generating either or both these errors. My system (Windows 7 64bit, 4Gb RAM, XAMPP 1.7.1, latestDrupal modules). I'll update this thread if I can narrow down the problem further.

EDIT: I should have added that Panels preview mode works fine showing selected content. "Page not found" error pops up 100% of the time if I click on the panels summary path link or re-key into the browser (for example: http://localhost/drupal/test-4).

Update: With a fresh, minimal install (core plus ctools + panels) I'm not getting any "page not found" or memory errors. I'm going to test further to see if this was an Omega theme/omega panel layout induced problem but to avoid clogging the thread unnecessarily I won't reply again unless anyone requests more details.

I'm getting this as well. I did just update to most recent CTools and Panels releases (dev). Working on a site brought over from 5 to 6, then right to 7. Lots of modules installed. Let me know if you hit a hiccup on your site again and have any idea what's causing this! Thanks.

I would highly doubt that an upgrade from 5 --> 6 --> 7 would have properly upgraded all of the panel pages. You will have to check all of them manually and possibly rebuild them.

Unfortunately without a way to reliably reproduce this to figure out what conditions cause this, there's not much I can do here.

We need people to help us reproduce this.

Hi

Please check http://drupal.org/node/1376930#comment-5384076 for a possible fix.

Not sure if it's related

Thanks

@GlitchFreak, thanks for cross-posting, I hadn't seen this issue otherwise :)
I think actually I will close yours as a dup of this one, so we can keep the information collected in one place.

Regarding your specific post, in #1376930: Panel Page Path is not working (with possible fix), you don't mention how, or that, you map the parameter to a context, so that's a possible problem. Nor do you mention that you have actually checked that entity 55 exists, or whichever type is relevant.

Since the average bug report is actually a configuration error, I prefer keeping it in the support request category until we've proven otherwise.

I can't reproduce this problem with the latest dev version, neither with a new panel page, or the export from #1, so a reproducing export would be useful.

Hi Letharion

I've created another Panel Page, and included an export at the end of the post. I haven't assigned any contexts as I don't require one.

The same error exists, i.e. I get a 404 when trying to view the page with an argument (www.example.com/lifegroup/77). Node 77 exists.

The code segments below are a comparison between a non-working panel page and a working panel page. This is where I think the problem lies.

My fix on the linked issue that was closed still solves my issue.

Non-working Page (current dev version)

$page->arguments = array(
  1 => array(
    'id' => '',
    'identifier' => '',
    'argument' => '',
    'settings' => array(),
  ),

Working Page (alpha3 version)

$page->arguments = array(
  1 => array(
    'id' => 1,
    'identifier' => 'Node: ID',
    'name' => 'entity_id:node',
    'settings' => array(),
  ),

So it seems that when the page is created, the code segments are not populated correctly. I've followed the exact same process of creating the pages with both versions.

Here is the export:

$page = new stdClass;
$page->disabled = FALSE; /* Edit this to true to make a default page disabled initially */
$page->api_version = 1;
$page->name = 'lifegroup_portal';
$page->task = 'page';
$page->admin_title = 'LifeGroup Portal';
$page->admin_description = '';
$page->path = 'lifegroup/%1';
$page->access = array();
$page->menu = array();
$page->arguments = array(
  1 => array(
    'id' => '',
    'identifier' => '',
    'argument' => '',
    'settings' => array(),
  ),
);
$page->conf = array(
  'admin_paths' => FALSE,
);
$page->default_handlers = array();
$handler = new stdClass;
$handler->disabled = FALSE; /* Edit this to true to make a default handler disabled initially */
$handler->api_version = 1;
$handler->name = 'page_lifegroup_portal_panel_context';
$handler->task = 'page';
$handler->subtask = 'lifegroup_portal';
$handler->handler = 'panel_context';
$handler->weight = 0;
$handler->conf = array(
  'title' => 'LifeGroup',
  'no_blocks' => 0,
  'pipeline' => 'standard',
  'css_id' => '',
  'css' => '',
  'contexts' => array(),
  'relationships' => array(),
);
$display = new panels_display;
$display->layout = 'twocol';
$display->layout_settings = array();
$display->panel_settings = array(
  'style_settings' => array(
    'default' => NULL,
    'left' => NULL,
    'right' => NULL,
  ),
);
$display->cache = array();
$display->title = 'LifeGroup';
$display->content = array();
$display->panels = array();
  $pane = new stdClass;
  $pane->pid = 'new-1';
  $pane->panel = 'left';
  $pane->type = 'views';
  $pane->subtype = 'lifegroup';
  $pane->shown = TRUE;
  $pane->access = array();
  $pane->configuration = array(
    'override_pager_settings' => 0,
    'use_pager' => 1,
    'nodes_per_page' => '10',
    'pager_id' => '0',
    'offset' => '0',
    'more_link' => 0,
    'feed_icons' => 0,
    'panel_args' => 1,
    'link_to_view' => 0,
    'args' => '%1',
    'url' => '',
    'display' => 'page',
    'override_title' => 0,
    'override_title_text' => '',
  );
  $pane->cache = array();
  $pane->style = array(
    'settings' => NULL,
  );
  $pane->css = array();
  $pane->extras = array();
  $pane->position = 0;
  $pane->locks = array();
  $display->content['new-1'] = $pane;
  $display->panels['left'][0] = 'new-1';
$display->hide_title = PANELS_TITLE_FIXED;
$display->title_pane = '0';
$handler->conf['display'] = $display;
$page->default_handlers[$handler->name] = $handler;

Are you sure? This kind of looks like you didn't go through and populate the argument.

I'll doublecheck but I'd like to be absolutely sure you went to the 'arguments' tab and populated an argument.

Ah, thanks for pointing that out. I populated it and it now works.

I'm sure I didn't have to do it previously, however I could me mistaken.

Thanks merlinofchaos and Letharion for all the assistance.

No, you have always had to do this; unless you tell it what kind of data the argument is, it doesn't know.

Thanks merlinofchaos. I'll remember this for the future.

hi, all
I have the same issue but i don't know how populate an argument in panels. someone help me please!
I can not create new pages with panels anymore ( i have two working ones).

I ran into a similar issue trying to create a 404 page. Giving the page an "Administrave Title" of 404 created a machine name of 404. I don't think machine names starting with numbers are valid. Recreating the page with a machine name of "page-not-found" fixed my issue.

I hope this helps.

This is happening because after you delete a page that was set up to be the main site's page, the module is not emptying the site_frontpage variable

I found a great working solution.

The system panel pages that are already available (which you can enable or disable) do get their page titles set. But when you create custom panel pages with a path say foo-bar or dashboard/%foo and such paths are not declared in the hook_menu() of any of the contrib modules or your custom modules, you will get a Page not found set in the title. You would still see content if you have added any panes in your panel. You can set the page title in your panel settings, but that shows only in the <h1> tag in your page, but the <title> tag still shows Page not found.

You can use the metatag module to fix this. Once you have the module installed you can add (or override) page titles and other metadata by path here admin/config/search/metatags/context/add