Redirect Pro

lee · 2008-03-26 20:39:33

Thanks, much appreciated.

zero · 2008-03-27 14:32:30

Even though I am a subscriber to zem_redirect and I can login at the subscribers page and can see the downloads and articles available, when I click the Redirect Pro v1 Documentation, I get this response (and this has been the case for a long time):

Subscribers
Redirect Pro v1 Documentation
Purchase a subscription to zem_redirect now for instant access to downloads, documentation and support:
New subscriptions are currently unavailable.

So not even subscribers can access the documentation.

Now, what if a subscriber had the documentation somewhere on their computer. Could they legally pass it on to someone who needed help, whether for payment or for free? Isn’t that providing a service?

ruud · 2008-03-27 14:36:07

Nope. IIRC, the documentation was not released under a license that permits distribution.

zero · 2008-03-27 15:05:42

Yes, you do recall correctly, Ruud. As you previously pointed out, in the comments of this thread Alex states:

Please note that while the source code is GPL, documentation, support and regular updates are available to subscribers only.

and the last line of the last link states that:

Support services may not be transferred, sold, or provided by proxy to a third party.

Thankfully, the plugin does most things automatically!

lee · 2008-03-27 15:09:46

All these license safe guards are a good thing, but as zem is no longer making money from it or supporting it let’s hope he releases to the community for free.

Last edited by lee (2008-03-27 15:10:17)

els · 2008-03-27 17:38:45

zero wrote:

So not even subscribers can access the documentation.

I can.

In my opinion it isn’t wrong that I posted the tag attributes, because anyone can find those in the plugin code. And the use of the tag seems mostly self evident. The examples I posted were very simple and most people would be able to figure that out. Still, I think I shouldn’t have done that so I removed them.
The fact that many more – and more complicated – examples are given in the documentation is what makes it valuable. It’s a pity that it is just ‘locked’ somewhere, as new subscriptions aren’t possible and support doesn’t seem to be very available for subscribers either (I mailed zem a support question quite a while ago but never got an answer).

Last edited by els (2008-03-27 17:41:14)

ruud · 2008-03-27 17:54:33

Someone who has only the plugin code to could write a manual with useful examples without looking at the original documentation that zem provides and release that under a free license. Or perhaps even modify the plugin to include such a manual, especially if the plugin is no longer maintained (not sure if it is).

jakob · 2008-09-28 21:41:40

I have to say the situation with this plugin is quite ridiculous. I really respect Alex for his manifold contributions but the license situation has backfired here with no-one benefitting, neither him nor the users.

Would a kind soul be willing to whisper via mail some usage tips for redirecting static previous pages to txp pages? I’m no beginner but I’ve not worked it out with trial and error.

kevinpotts · 2008-10-19 02:21:47

I really agree with Jakob on this. Considering that no one has developed anything comparable, Alex has left the Textpattern scene, and new subscriptions are not available (I’d pay the $9 in a second if I could), it’s totally ridiculous that the documentation is not available. This is deadware. Can someone with some common sense please share information on how to use the plugin, because while I would love to support Alex and give him money for this stuff, he clearly does not want my cash.

jakob · 2010-12-14 17:03:23

Just passing on some information I learned the hard way: if you are trying to use this plugin to do a manual redirect and it just will not do what it is told, try switching the production status to “testing” or “live” in the settings. In debug production status it just smiles at you with a message but does nothing!! I realise this is actually meant to be a feature but without documentation to tell you that, how can you know… grrr

A usage example to redirect when the search function finds an article that is displayed on the section landing page but not linked to individually. Place the redirect function right at the very top of your page before the doctype:

<txp:zem_redirect to="/section" from="/section/article-name" /><!DOCTYPE html>....

Last edited by jakob (2010-12-14 17:03:59)

els · 2010-12-14 19:21:01

Thanks for posting Jakob! Not a bad idea at all. If we all just start posting usage examples and issues we encountered (and hopefully solutions), then maybe this thread can become sort of a support thread.

jakob · 2010-12-14 23:24:13

May I find out more by asking questions?

For example: I’m using tru_tags on the site in question and have lovely www.mysite.com/tags/tag-name clean urls for the tags section … that is until I activate zem_redirect (the version 1.2.1 neko posted above). Then it shows me the clean url for a brief moment before updating it to http://www.mysite.com/tags/?section=tags&t=tag-name. It only needs the plugin to be activated as there is no zem_direct tag in the tags page template (the zem_redirect tag mentioned above is in an entirely different page template).

Is there a way of making zem_redirect less aggressive in its interception? Or perhaps an alternative way of achieving what I posted earlier?

jakob · 2010-12-15 14:45:25

I think I have two possible solutions to the above. It seems to rest with tru_tags use of the url parameter &section=tags rather than &s=tags.

One solution is to edit zem_redirect and add unset($get['section']); to the following around line 75 so that it reads:

		# other unknown query parameters might be used by plugins
		$get = gpsa(array_keys($_GET));
		if (!$get) $get = array();
		unset($get['id']);
		unset($get['s']);
		unset($get['section']);
		unset($get['c']);

The other solution is to edit the function tru_tags_clean_url_handler in the tru_tags plugin around lines 494 and 497 replacing the GET['section'] and POST['section'] with GET['s'] and POST['s']. The respective section of code then reads:

		if (count($_POST) > 0) {
			$_POST['s'] = $tru_tags_prefs[TAG_SECTION]->value;
			$_POST[$tru_tags_prefs[PARM_NAME]->value] = $tag;
		} else {
			$_GET['s'] = $tru_tags_prefs[TAG_SECTION]->value;
			$_GET[$tru_tags_prefs[PARM_NAME]->value] = $tag;
		}

I’m not sure if there is a particular reason why tru_tags uses ?section= rather than ?s=. Maybe its root lies in an earlier version of txp. I’ll continue to watch what happens and report back if it goes up in smoke!

BBTW: both solutions together are not necessary.

Last edited by jakob (2010-12-15 22:13:27)

els · 2010-12-15 20:43:19

Thanks again! A couple of years ago I had exactly the same problem, and the only way to solve it back then was to stop using Redirect Pro… At the moment I’m not using the ‘tag’ section anymore, so the problem is gone. But I’m sure it will help others.

Or perhaps an alternative way of achieving what I posted earlier?

Don’t know. It’s exactly how I’ve been handling this.

Textpattern CMS

Textpattern CMS support forum

#31 2008-03-26 20:39:33

Re: Redirect Pro

#32 2008-03-27 14:32:30

Re: Redirect Pro

#33 2008-03-27 14:36:07

Re: Redirect Pro

#34 2008-03-27 15:05:42

Re: Redirect Pro

#35 2008-03-27 15:09:46

Re: Redirect Pro

#36 2008-03-27 17:38:45

Re: Redirect Pro

#37 2008-03-27 17:54:33

Re: Redirect Pro

#38 2008-09-28 21:41:40

Re: Redirect Pro

#39 2008-10-19 02:21:47

Re: Redirect Pro

#40 2010-12-14 17:03:23

Re: Redirect Pro

#41 2010-12-14 19:21:01

Re: Redirect Pro

#42 2010-12-14 23:24:13

Re: Redirect Pro

#43 2010-12-15 14:45:25

Re: Redirect Pro

#44 2010-12-15 20:43:19

Re: Redirect Pro

Board footer