Closed (fixed)
Project:
Panels
Version:
6.x-3.x-dev
Component:
Panel pages
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Apr 2009 at 11:51 UTC
Updated:
14 May 2009 at 22:10 UTC
I just got the latest code and created a test Page Panel (path /test) with one-column layout and a single node.
Went through the panel wizard, saved the panel, yet when accessing the URL mysite.com/test getting Page Not Found. Even if I create a menu item.
Is something broken in the module or do I have to set up something else for paths to work?
Comments
Comment #1
merlinofchaos commentedIt's hard to tell for sure what might be going on here with the information you've provided.
Did you fully save the panel? Did you add any access control? It would probably help if you export what you have saved and paste it here so I can see the settings you used.
Comment #2
dkruglyak commentedOK, so I decided to reproduce the process by deleting the panel and re-creating it from scratch.
1) Step one, start the wizard to create the panel 'test'
2) On layout screen choose "one-column"
3) On panel content screen choose single node, with teaser unchecked
4) When trying to save the content, wizard aborts and redirects to /admin/build/delegator/page-test
5) When I go /admin/build/pages, page appears as created/listed there, but navigation to /test produces "Page Not Found"
6) Export of the panel results in "Page Not Found" too
7) When I go to "edit" turns out the layout and contents did not get saved.
8) So I go to layout screen, pick my layout again and hit "Update & Return"
9) Now the layout and content load OK in edit screen, but "Page Not Found" still shows up on navigation and export
So probably some UI issue or saving issue and I cannot even think of a workaround...
Comment #3
cpelham commentedI am getting the same problem. I have been able to replicate it. Unfortunately, I also cannot export the panel pages, though I can go back and edit them (including the path) so I know they are being saved.
Comment #4
merlinofchaos commentedI'm starting to wonder if the version in this bug report is correct. Is this really alpha4 or or this against -dev? (This matters because after alpha4 I added a new page type on the admin/build/pages list, so there are 'simple pages', 'custom pages', and 'panel pages'. And the new page type was in but didn't work until quite recently).
Comment #5
cpelham commentedI just updated to the latest dev to see if that would fix it but no dice.
Comment #6
dkruglyak commentedI have been using the latest too. Could you suggest where to look for root cause of path not being created?
Comment #7
cpelham commentedI am looking at the delegator table in the database.
Here is some of the info for one of my pages (but I suspect that the nid that the path points to, if indeed a nid is created for a panel page, is stored elsewhere?):
pid: 2
Name: Healing
task: panel_page
path: healing2
menu long text:
a:5:{s:4:"type";s:6:"normal";s:5:"title";s:7:"Healing";s:4:"name";s:13:"menu-channels";s:6:"weight";s:1:"0";s:6:"parent";a:4:{s:4:"type";s:4:"none";s:5:"title";s:0:"";s:4:"name";s:10:"navigation";s:6:"weight";s:1:"0";}}
conf long text:
a:4:{s:9:"no_blocks";i:0;s:6:"css_id";s:0:"";s:3:"css";s:0:"";s:7:"display";O:14:"panels_display":13:{s:4:"args";a:0:{}s:7:"content";a:2:{s:5:"new-4";O:8:"stdClass":13:{s:3:"pid";s:5:"new-4";s:3:"did";i:0;s:5:"panel";s:3:"top";s:4:"type";s:5:"block";s:7:"subtype";s:6:"user-2";s:5:"shown";i:1;s:6:"access";a:0:{}s:13:"configuration";a:6:{s:14:"override_title";i:0;s:19:"override_title_text";s:0:"";s:6:"module";s:4:"user";s:5:"delta";s:1:"2";s:16:"block_visibility";i:0;s:14:"block_settings";a:1:{s:26:"user_block_whois_new_count";s:1:"5";}}s:5:"cache";a:0:{}s:5:"style";a:0:{}s:3:"css";a:0:{}s:6:"extras";a:0:{}s:8:"position";i:0;}s:5:"new-3";O:8:"stdClass":13:{s:3:"pid";s:5:"new-3";s:3:"did";i:0;s:5:"panel";s:10:"left_above";s:4:"type";s:5:"block";s:7:"subtype";s:12:"statistics-0";s:5:"shown";i:1;s:6:"access";a:0:{}s:13:"configuration";a:6:{s:14:"override_title";i:0;s:19:"override_title_text";s:0:"";s:6:"module";s:10:"statistics";s:5:"delta";s:1:"0";s:16:"block_visibility";i:0;s:14:"block_settings";a:3:{s:28:"statistics_block_top_day_num";s:1:"0";s:28:"statistics_block_top_all_num";s:1:"0";s:29:"statistics_block_top_last_num";s:1:"0";}}s:5:"cache";a:0:{}s:5:"style";a:0:{}s:3:"css";a:0:{}s:6:"extras";a:0:{}s:8:"position";i:0;}}s:6:"panels";a:7:{s:3:"top";a:1:{i:0;s:5:"new-4";}s:10:"left_above";a:1:{i:0;s:5:"new-3";}s:11:"right_above";a:0:{}s:6:"middle";a:0:{}s:10:"left_below";a:0:{}s:11:"right_below";a:0:{}s:6:"bottom";a:0:{}}s:16:"incoming_content";N;s:6:"css_id";N;s:7:"context";a:0:{}s:3:"did";s:3:"new";s:6:"layout";s:13:"twocol_bricks";s:15:"layout_settings";a:0:{}s:14:"panel_settings";a:0:{}s:5:"cache";a:0:{}s:5:"title";s:0:"";s:10:"hide_title";i:0;}}
Comment #8
cpelham commentedCould this error message in my logs be part of it?
Missing argument 2 for delegator_page_export_subtask() in /Users/cpelham/Sites/drupal/drupal/sites/all/modules/ctools/delegator/plugins/tasks/page.admin.inc on line 1433
Comment #9
DanielJohnston commentedSubscribing.
Comment #10
summit commentedSubscribing, greetings, Martijn
Comment #11
kmontyI had the same error with -dev but not with alpha4. I wanted to use some of the new content-type functionality but I'll just wait for the beta now.
Earl, here is my export so you can replicate. To summarize: I can generate a preview within Panels, the menu-item appears fine however when I attempt to access the panel via the path alias I receive a 404 "Page not found
The requested page could not be found."
Comment #12
dkruglyak commentedChanging title to hopefully draw more attention to this confirmed problem.
Comment #13
kmontyUsing dev snapshot from April 24th.
I traced down the issue (at least on my end). If I setup the panel page with the path "test/" and then attempt to go to www.mysite.com/test/ I will receive a 404.
If I setup another panel with the path "anothertest" and then attempt to go to www.mysite.com/anothertest/ it is fine.
The Path field description mentions nothing of this limitation. My suggestion would be to fix this or put "Do not add a trailing slash to the path" wrapped in a strong tag in the #description.
Comment #14
merlinofchaos commentedkmonty: Ahh! Thanks for figuring that out for me. I have checked in a fix, and this should work in beta1.