See #820374: URL redirect task handler (page manager redirect) comment #11.
So there's a CTools HTTP Response Code handler. Page_manager_redirect might as well be deprecated then, so:

  1. Tie up any loose ends in page_manager_redirect
  2. Create an upgrade path to convert existing variants to HTTP Response Code variants
  3. Any further features/ideas should go towards the HTTP Response Code handler:
    1. Create patches for drupal messages (see #1064602: Optionally show a Drupal message on redirects) for HTTP Response Code
    2. Patch HTTP Response Code for choosing an exact HTTP code (not just 404/403/301)?

Comments

lpalgarvio’s picture

lpalgarvio CreditAttribution: lpalgarvio commented

+1

rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
CreditAttribution: rootwork commented
Title: Get to feature parity with CTools HTTP Response Code handler & make upgrade path » Get to feature parity with CTools HTTP Response Code handler & make upgrade path and documentation

It would be great to, at the very least, provide some documentation as to how the HTTP Response Code handler will allow people to achieve what Page Manager Redirect does. I'm just finding this module now, and on the project page, there's a big notice that suggests using the HTTP Response Code handler in CTools is the way to go -- but there's vanishingly little documentation about that handler, and certainly nothing specific to achieving what this module does.

I'd like to help document this, but as I'm new to the module, I don't know enough to help yet. And since there's no information on using the CTools handler, I'll go ahead and use this module, even though it seems like it will soon be depreciated.

My guess is that most other new users will make this decision too, unless someone familiar with this module can suggest how to achieve the same thing with the CTools handler. (Unless you're on the verge of creating an upgrade path, in which case it doesn't matter and everyone can just use that.)

james.williams’s picture

james.williams CreditAttribution: james.williams commented
Title: Get to feature parity with CTools HTTP Response Code handler & make upgrade path and documentation » Get to feature parity with CTools HTTP Response Code handler & make upgrade path

I'm reverting the issue title because there is the other issue about documentation (#842944), this issue is something different.

There is a link to the documentation on the project's page. (In the right sidebar, 'Read documentation'). This is the documentation page: http://drupal.org/node/938584

The HTTP Response Code handler in CTools is virtually the same in how to set up a redirect, the main difference being that you enter the full URL (with fragment/query) in one box, rather than three separate boxes as in PMR. Please understand I am not responsible for the HTTP Response Code handler, that is part of CTools core.

I am not currently proceeding with any urgency on this particular issue (getting to feature parity & making an upgrade path), since both are relatively simple if you understand Page Manager handlers (hopefully the documentation might help with this).