Re: When will SEO be integrated?

« Reply #37 on: August 28, 2005, 05:00:17 AM »

Saka
Development Workgroup
Full Member

Quote from: guilliam on August 27, 2005, 09:09:58 PM

^^based on this statement,.. i just wish to confirm that IF the *ambo DB is restructured so then the advance SEF will be integrated?

IF then, that would answer the question of @malibu in this thread's title.

Yes. That's what I've been saying all the time. And it has been on the roadmap for future versions (5.0) together with unlimited level of categories and node base content structure.
It will be new URL solution totally based on the new structure of core, both non-SEF and SEF URLs will be changed.

Re: When will SEO be integrated?

« Reply #36 on: August 27, 2005, 09:09:58 PM »

guilliam
Forum Workgroup
Joomla! Hero

Quote from: Saka on August 27, 2005, 12:36:40 PM

Quote from: kenmcd on August 26, 2005, 04:53:31 AM

Could money be an issue?
1,000 buyers x 40 Euro = 40,000 Euros.

Again I don't have nearly as many customers. However as I said SEF advance requires considerable load of work every day. I can't do that for free, but am doing many other things for Mambo for free.
It's simply NOT TRUE that better SEF is not being added because I am selling a component that does that. I never oposed making the better SEF in core. If you make clean, maintenance free and bug free solution we will integrate it today! It's just my opinion that it can't be done before Mambo is restructured from ground.

^^based on this statement,.. i just wish to confirm that IF the *ambo DB is restructured so then the advance SEF will be integrated?

IF then, that would answer the question of @malibu in this thread's title.

Reply #35 Omitted

Re: When will SEO be integrated?

« Reply #34 on: August 27, 2005, 12:36:40 PM »

Saka
Development Workgroup
Full Member

Quote from: kenmcd on August 26, 2005, 04:53:31 AM

Basically it means that when someone is losing the argument based on the facts, they turn to bashing the opposing party.

I bashed you? I gave you the reasons why I haven't integrated SEF advance into the core, and the reasons are technical. If you would know more about Mambo, its programming and structure you would know that those reasons are facts. I suggest you read my previous post again and not concentrate on the "bashing" part.

Quote from: kenmcd on August 26, 2005, 04:53:31 AM

So far I am ignorant, evil, and lazy.

It wasn't personal. I was talking in general. This has been discussed many times before.

Quote from: kenmcd on August 26, 2005, 04:53:31 AM

The performance issues don't seem to bother the hundreds (thousands ?) of people who are running SEF Advance.
The issue of performance has nothing to do with open source.

I wish I had thousands of customers.  However the performance isn't the only issue here. I explained very clearly several reasons among which maintenance, support etc.
I spent many years developing Mambo and custom solutions for Mambo. 90% of my contribution you are using for free. However SEF advance is not free, but nothing stops you or anyone else to write your own solution. Go ahead!

Quote from: kenmcd on August 26, 2005, 04:53:31 AM

Could money be an issue?
1,000 buyers x 40 Euro = 40,000 Euros.

Again I don't have nearly as many customers. However as I said SEF advance requires considerable load of work every day. I can't do that for free, but am doing many other things for Mambo for free.
It's simply NOT TRUE that better SEF is not being added because I am selling a component that does that. I never oposed making the better SEF in core. If you make clean, maintenance free and bug free solution we will integrate it today! It's just my opinion that it can't be done before Mambo is restructured from ground.

Quote from: kenmcd on August 26, 2005, 04:53:31 AM

"Pretty much the only "hook" into Mambo's core, to allow any significant third-party extension to Mambo's base functionality without modifying the core files, is the SEF support. (A cynical person might argue that even this "hook" exists only for the benefit of a certain commercial SEF extension developed by a core developer.)"

The hook was provided to enable easy install of all SEF components out there, not only SEF advance. In that moment there was 3-4 other SEF components out there and they all made use of this hook. If I wanted only SEF advance to be supported I wouldn't have done it that way.

Quote from: kenmcd on August 26, 2005, 04:53:31 AM

I had suggested it be renamed OpenSEF going forward.

I wish you all the best. It's only good that there are several SEF solutions out there before we redesign the Mambo's structure and make it suitable for more advanced SEF in the core.

Reply #34 Omitted

Reply #33 Omitted

Reply #32 Omitted

Reply #31 Omitted

Reply #30 Omitted

Reply #29 Omitted

Reply #28 Omitted

Reply #27 Omitted

Reply #26 Omitted

Reply #25 Omitted

Reply #24 Omitted