Topic: AceSEF & SOBI2 & XMap

[Trinity]

"But non native SEF components don't play well with SobiSEF (or any other native router file)" 

As I already stated in another post, creating search engine friendly URLs by a (non native) SEF component is the "old way" of creating FURLs. This is not the idea behind Joomla native SEF.

If each component would have its native router file, there will be no need for SEF components. I think this is also the reason why the most SEF components have increased their functionality like meta or sitemap control. In this way they still have a right to exist 
 
SEF components are still needed because the most component developers don't develop native router files for their components, what is a pity 

Trinity

[denisdulici]

Trinity - With all respect, I don't think that the SEF components age will end until J! Devs will develop a SEF component  As far as I know, only SOBI2 has a plugin that offers you to handle and "modify" your URLs. However, the Joomla native SEF does not offer you such a feature.

Also, Joomla native SEF URLs are not "focused" as SEF components which is the main issue for SEO folks.

I'm not going to mention about the facilities of SEF components such as handling the SEO of all components from one window...

So I would not call using SEF components as an "old way" at all

[neo]

Trinity - With all respect, I don't think that the SEF components age will end until J! Devs

With all respect: have you indee read what Trinity wrote 

As far as I know, only SOBI2 has a plugin that offers you to handle and "modify" your URLs.

SEF components are still needed because the most component developers don't develop native router files for their components, what is a pity 

I'm not going to mention about the facilities of SEF components such as handling the SEO of all components from one window...

I think this is also the reason why the most SEF components have increased their functionality like meta or sitemap control.

[Belaire Technologies]

I'm actually hoping the joomla 1.6 makes SEF native no matter what extension you are using.

Already Joomla 1.5 creates FURLs for other extensions. But this is limited by nature. Joomla does not know how a component creates an URL. E.g. Sobi2:
From where Joomla should know that a Sobi2-URL has a part which is called "sobi2Task"?
From where Joomla should know that if "sobi2Task=sobi2Details" the details view of an entry is shown and the title of the shown entry which is stored in one of the Sobi2 tables, which Joomla does not know, has to be used to create a search engine friendly URL?
Same with the category names. From where Joomla should know when and how to create a URL with the name of a Sobi2 category?




You see, it is not possible for Joomla to create FURLs for 3rd party extension as you expect. Joomla already "hides" the Itemid, because this is a known part of the URL.

And this is also not possible for any SEF component. Each SEF component needs a specific file for each component where the "rules" for creating SEF URLs for a component are specified.

This is the same with Joomla. If the author of a 3rd party component writes a Joomla router file which specifies the rules for creating the FURLs, Joomla uses this file to create search engine friendly URLs. This is what SobiSEF does. SobiSEF is a Joomla router file for Sobi2 component to create SEF URLs for Sobi2 without the need of a SEF component - just Joomla native.

Trinity

Well said trinity and a good thought out reply to my less thought out comment.

I should have said that I hope joomla 1.6 gives a user more control over sef URLs.  It would be nice to have something native like Ace where 3rd party apps like Sobi2 just needs the router file.  Then at the joomla level you control the sef, meta, etc.

[ghost999]

I'm actually hoping the joomla 1.6 makes SEF native no matter what extension you are using.

Already Joomla 1.5 creates FURLs for other extensions. But this is limited by nature. Joomla does not know how a component creates an URL. E.g. Sobi2:
From where Joomla should know that a Sobi2-URL has a part which is called "sobi2Task"?
From where Joomla should know that if "sobi2Task=sobi2Details" the details view of an entry is shown and the title of the shown entry which is stored in one of the Sobi2 tables, which Joomla does not know, has to be used to create a search engine friendly URL?
Same with the category names. From where Joomla should know when and how to create a URL with the name of a Sobi2 category?



You see, it is not possible for Joomla to create FURLs for 3rd party extension as you expect. Joomla already "hides" the Itemid, because this is a known part of the URL.

And this is also not possible for any SEF component. Each SEF component needs a specific file for each component where the "rules" for creating SEF URLs for a component are specified.

This is the same with Joomla. If the author of a 3rd party component writes a Joomla router file which specifies the rules for creating the FURLs, Joomla uses this file to create search engine friendly URLs. This is what SobiSEF does. SobiSEF is a Joomla router file for Sobi2 component to create SEF URLs for Sobi2 without the need of a SEF component - just Joomla native.

Trinity

Well said trinity and a good thought out reply to my less thought out comment.

I should have said that I hope joomla 1.6 gives a user more control over sef URLs.  It would be nice to have something native like Ace where 3rd party apps like Sobi2 just needs the router file.  Then at the joomla level you control the sef, meta, etc.

Hi Belaire Technologies,

for me Sobi2, SobiSef, Joomfish simply do not work together (I think that it is not working for anyone).

So based on your recommendation, I have bought and installed Acesef (2d ago - last version). It is nice component with plenty of options. I have installed their component for sobi clones (I have 4 sobi clones  ).  I was able to setup all as expected...urls are nice, even when I switch language. However performance is  really, really bad. From average 2s/page I have  5/10s and sometimes even 404....
For me personally page speed is more important than SEF urls.

It is also somehow conflicting with Joomfish cache (problems clearing cache RefTableSql). I have played 2 days with cache settings in Acesef, Joomfish and Joomla...but no success.

Important to say - My website has 4 clones. Three of these clones have about 300 categories each.
However I have max 10 test entries...as it is still in development.
When I switch off AceSef performance is back to normal....(and part of the url - [expect sobi 2 part] is sef - I have joomla SEF activated).

Do you have idea what did I wrong? I posted same question on Acesef forum. However I think you could have some experiences and help me even more. How are you using acesef? Are you using it on big directory site with many entries? What is overall performance of these sites?


This is my config :
Server: Apache
Platform: 2.6.18
PHP Version: 5.2.14 (cgi)
MySQL Version: 5.0.91   
PHP Memory Limit: 94 MB
PHP Script Execution Time: 30 Seconds
PHP Safe Mode: disabled
CMS RG Emulation: disabled
GD Library: installed
iconv/mbstring Library: installed
Charset: utf-8
Database Collation: utf8_general_ci
CMS: Joomla! 1.5.20
Sobi2 : 2.9.3.1
Joomfish: 2.0.4

Thank You.

Regards,
Pavol