Joomla! Discussion Forums

I disagree. RSS feeds are backlinks, and they have changed in Joomla 1.5. Now, you could argue that a new legacy module would have to be written, but it's possible the legacy code implemented could be tweaked to add support.

And, we still don't know if it hasn't already been implemented. You seem anxious to close this thread, I'm not sure why.

Sorry, been off the reservation for a while.

I totally agree that we are not done yet.

First, at first glance I see mention of a 302 temporary redirect.  That is not the same as a 301 permanent redirect. We want to convert old links in to the new system, not tell Google that the links will be back at their old location some day.

I installed the latest build, but still am testing through. I am still having trouble getting any of the old links to work correctly, temporary or otherwise redirected.  As mentioned above, there are still all the issues of components and other SEF url layouts and such to be sorted out. Lance's solution may very well still be needed.

This is a good start, just there is a lot of testing ahead, and likely tweaking that this thread is the best place to do it in, rather than splitting the issue across multiple threads when most of the core issues and goals have already been defined. 

I saw the note about 302, but I thought there was an option... okay, removing solved.

The importants of 302 vs 301, in case it's not perfectly clear, is that accumulated PageRanks from 302 redirects do not transfer like 301's do. Meaning, if you got an article digged and slashdotted about 10 times, Google won't drop the article from the cache... but they don't promise you'll still get PageRank credit either.

Since the old links aren't in-use anymore, they have permanently moved to the new 1.5 structure. As such, they should be 301 Permanently Redirected.

Now, it isn't clear how search engines handle 302's. Google & Co don't want to tip their hat on that, since it could allow for people to abuse more easily (after all, if you know how they treat 301's differently from 302's, you can better set up SERP attacks based on the distinction).

However, in this case, a 302 isn't needed... the articles aren't temporarily moved when you've migrated. If you go back to Joomla 1.0 (which I shudder at the notion, I'd rather go to WordPress or Drupal at that point), but the redirect will be dropped and the pages re-indexed.

Better get busy then! 

Thanks for the words of encouragement! The good news is that the code is checked-in, so now we can start to regress these issues and post them as bugs in Q&T. This thread has sparked a lot of great general discussion, now we're at the point where we can isolate issues with existing code... rather than having to address a crisis in general terms.

Tomorrow, when I have more time, I'll pin down a few things for Q&T and report them in. Then, I'll probably start a new thread to follow-up and we'll isolate further in this forum.

Now, you got my thumbs up! Providing bug reports (fixes are appreciated but not everyone can code) is contributing and opening a new thread would be very much appreciated.

Thanks sincerely! Here's to Joomla! v 1.5! May it do good in the world!
Amy

please keep us informed as the issues get split in to their specific parts. I have not had a chance to look at exactly how they implemented this, but it would seem kicking out a 301 response would not be that big of a leap. It is one digit after all.

Issues outstanding it would seem would be component generated link handling for 301 redirects. 

say, when was the fix applied to the nightly builds?  I am suspecting I have the wrong build (yesterday), but I am not seeing 302 header responses and links are still broken when SEF or any other combination is turned on. Without SEF things are working.

Where in the code do I look for the modifications they made to produce the 302 redirect? 

Cenc -

It is the System - Legacy plugin and you must enable the "Use Legacy URL Routing" parameter to invoke the logic. (Select Extensions - Plugin Manager in the backend Administrator. )

If you want to look at the actually code, you should find it in the plugins\system\legacy.php file.

The best place to report errors is the Joomla! 1.5.x_Q&T threads and they appreciate it if we follow the Bug Report Template guidelines Robin put together.

Hope that helps!
Amy

Hi all, back again. Sorry for my abrupt departure, but First Life™ took priority. I've set up a general catch-all topic in Q&T since 1.5 hasn't gone stable yet. Please isolate issues in that thread so that they can be made into specific cases to be tracked and fixed:

http://forum.joomla.org/index.php/topic,227670.0.html

2 more cents...
Ditto on hatoncat being "impolite" -- from the very beginning. Glad the issue got worked on.
Railer

It appears that CatonHat has migrated to WordPress.

I will ask if this thread can be locked since those willing to help can continue the Legacy Backlinks work in the Q&T area.

Amy

There was absolutely no need for that comment. Flaming just for the point of attacking a user is against the forum guidelines, and it is obvious that I have made clear that my tone was not impolite, but simply drawing attention to a major flaw in Joomla 1.5.

However, I do agree that this thread should be closed, it is no longer needed since this issue has, for the most part, been resolved and should be moved to Q&T.

While it is indeed true that I have begun migrating sites to WordPress, it is because of a combination of several problems in Joomla, that do not appear to have matured enough in 1.5 for our operations. I don't need to go into all those reasons here... folks are free to read up on them elsewhere. We are still using Joomla for our primary operations, and will continue to do so at least until the end of the year.

Railer has just as much of a right as you do to observe what he sees as a community problem. Frankly, I agree with his observations, 100%.

Since the original poster has requested a close to this thread, perhaps, now, we can now conclude this matter?

For all who are interested, there is a system plugin available named Backlink that you can use for legacy backlinks. The community could use a few interested parties to provide feedback to the development team regarding this work. Please provide feedback in the Q&T thread.

Amy

My problem was with Joomla's future. Railer's is with an individual. That's where the guidelines come into play, so no, your assertion is incorrect.

And that, is all I have to say in this thread. Hopefully it will be closed soon.

I am committed to Joomla!'s future. Every single day, I come to these forums and I do my very best to help new community members learn how to use Joomla!. I blog about technical matters I believe are relevant to Joomla!. I try to lift up and encourage contributors - those who are *doing* something to make Joomla! better. I have worked to identify success stories to show that Joomla! is helping people in the world, both in my blogging and my sharing the sites, themselves, made possible by these people.

Joomla! is made available by volunteers. People who *freely* give of their time and their talent. The only way we, as a community, will "commit suicide" as you have repeated as your concern, is by discouraging our contributors. That is what happened in this thread. That is why Railer was correct to stand up against it!

Keeping things fun and interesting and hopeful and encouraging is the number one priority in an open source community. Anyone can point out problems. It takes someone very special to offer a solution freely. And, so they have. There is a plugin available for legacy backlinks. It was always on the list. There is just a very long list of needs and a very short list of contributors who have no more time available than anyone else.

Amy

At the request of the parties in the thread and also due to the wandering nature of the posts, this thread has been locked.