Aliases paths require both alias and non-aliases version to be added to list of paths

Do you get any javascript errors?

I had a similar issue but for any sort of page using the overlay with this module (and similarly using this approach for example - http://drupal.stackexchange.com/a/8265/7279).

I tracked it down to my theme which had an overlay.tpl.php file. When i removed that then it worked fine.

Random.

Could you comment on what steps you took to track things down?
I am having the same re-direct issue, and I am using the ZEN theme that doesn't have a overlay template that I can see; in the base theme or the sub-theme.

- no javascript errors that I can see from the firebug console

Hi,

I have the same issue but with a js error displaying, right before redirection :
---------------------
$(window).on is not a fuction
$(window).on ( 'smartresize.eislideshow', fuction( event ) {
---------------------

Can you help me ?

@jmhead Could you provide some steps to reproduce the issue? What paths do you have set up for appearing in the overlay, and how do links to those paths appear on the page?

Same problem here. The link is generated by views. The Target is (for example) tcm/testcase/5. In our config we have tcm/testcase/*. Any idea? We have no overlay.tpl.php in our Theme (Bartik).

Greetings,
Rico

I had this problem suddenly one day, even though it was working correctly the day before. Turned out that it was due to a multi-domain installation. The content I was clicking on was not in the same domain (subdomain) as the domain I was in.

Actually, even though I know how to get around this problem, it still is a problem because that means I can't share content across domains and expect the overlay to work. It is based off of the source domain of the content, of which there can only be one. So I can't make the overlay work for the same content in multiple domains.
Does any know of a workaround or patch for this?

Don't know if any of this helped the original poster, but I found out that to make overlay paths work across domains, I needed to make the Source Domain "Use active domain".
I was originally taking that to mean "the domain I'm in now when editing content", but it must actually mean "the active domain at the time of render".
Not the first time simple textual indications have confused me and caused hours of lost time...

Don't know if this helps anyone here but I resolved a similar problem by including the original path ie. node/1 and also its corresponding url alias ie. content/my-node. For some reason, in some scenarios only using the core path was breaking the overlay.

confirmed - I had the same redirection problem here. However, when adding the original node path like node/15 via hook_admin_paths_alter, the overlay shows up correctly (for both the original path and the path alias).

Yes, I have the same here. Bartik, nothing special, I try to use the example module to add a node (any) and it redirects. The url I'm using is node/*/school-terms/dashboard.

Maybe is just the UI of the example module that is not listening, but I get or redirects or simply nothing.

Thanks

Same problem here but with Drupal 7.15 on nodes view.

The overlay load the grey screen and then redirect to the normal node page.

I have an "alert"(yelllow) on firebug console when this appened:

"Has not been declared character encoding of a document set in a frame. The document may look different when viewed outside of the frame."

Any solutions?

do you definitely have both paths in the overlay paths list, for the page you want in overlay? The core path... ie. node/2 and pathauto alias too. Without pathauto installed it seems to work fine with just the core path, but with pathauto installed you must include both paths... at least I needed to with my installation.

Hope that helps.

@scubox

adding node/* to the list it seams to fix the issue!!! Really TNX TNX TNX you saved my day.

Hi,

I'm having the same problem that posted in original post. I'm using Drupal 7.16, Overlay Path 7.x-1.1, Pathauto 7.x-1.2.

I defined a content type named 'consulta', and defined a path alias 'consulta/[nid]' for that content type. When I define the overlay pahts list like 'consulta/*' and try to open a 'consulta' page the system just redirect the users to the 'consulta' full content page, don't try to open it in a overlay neither show the '#overlay=...' url. When I add the 'node/*' pattern to the overlay path configuration (besides the 'consulta/*' path), it's try to open the full content page in overlay, but finally redirect the users to the full content page.

Now, when I configure a path to a specific content (like 'content/50') and put 'node/50' in overlay path configuration list, and I try to open that specific content it open in overlay.

So, in order to have overlay working with specific path alias, I had to configure a path to specific content id, but wildcards do not do anything for that path.

I cleaned Drupal's and browser's cache, but the results are the same. There is not javascript errors.

I can confirm that I have the same behaviour.
Drupal 7.17
Latest overlay_path-dev version

I added the line "node/8" and now it seems to work ok.

Same here. All latest stable releases. I would like to only show one content type in a overlay. So node/* is not an option. Anyone figured out how to do this?

Updated the title of the issue, and marked as a bug report, though this might actually be a bug in core.

quick patch

Patch in #22 fixes the issue for me (using simplytest.me to test)

Thanks for the patch, I've committed it to 7.x-1.x I'll roll a release soon.

Actually, we can possibly do better, performance wise, here's a patch against 7.x-1.1 for simplytest.me to chew on.

Should I post in here that views URL paths don't work or start a new issue?

If I create an overlay link to a view page, it just gives the blacked out window. Since there is no "core" url path to it, I have no way of doing the "add both" trick :-/

@philsward start a new issue please.