Steps to replicate:

Create a panel page with a path of "test/%test" and on the arguments screen, do not assign any context to the %test argument. If you try to visit "test/foo" it will give a 404 page not found error.

Comments

jhchnc’s picture

jhchnc commented

Confirmed -- if it wasnt' for this post i'd be lsot.

Also, adding the context to the argument fixed the 404.

The issue is this -- yes, I'm using an arguement, but i'm using it in the custom module which builds the block on that panel page. I'm not using it in a "Panels" way.

Anyway, thanks for Panels :)

Letharion’s picture

Letharion commented
Status: Active » Postponed (maintainer needs more info)

I'm probably not seeing all the angles here, but can someone tell me what you would expect instead. I don't see how this is a bug?

Letharion’s picture

Letharion commented
Category: bug » support
Status: Postponed (maintainer needs more info) » Closed (won't fix)
nafmarcus’s picture

nafmarcus commented

Same problem. In my case, I'm passing one argument to the panel, a list of nodes separated by commas. There is no context associated with this list. The list, as argument 1 of the page, is then passed to a view panel that is expecting a list of nodes.

But whenever I try to call the panel, it tells me Page Not Found.

To be specific, I defined a page with a path of /interest/%prodList and if I call
[mySite]/interest/19273,19274, it returns Page Not Found.

nafmarcus’s picture

nafmarcus commented

Although the argument in the url doesn't really have a "context" you can set the context to String and then it seems to work.