burek
Results 1 - 2 of 2
One MAJOR flaw of this component is it doesn't have constantly updated sef extensions. Since, the developers are the only persons who really know the structure of their component/database, they are surely responsible for updating those extensions.
On your forums, I've read nothing but blaming other people, like developers of all those SEF components, for not updating their extension list with one for RSGallery.. This could really be a big problem for this component.
Also, the developers of this component are also responsible for keeping their content elements files (for JoomFish), the same reason as above..
Oh yes, I almost forgotten another very important thing. While I was trying to somehow develop the SEF extension for myself (since no extensions found on the internet were good enough for me) I've realized you are using $catid and $limitstart variables (altogether with page=inline) to display a singe image. Is this really necessairy? For example, you could use only $id (like for download link) and from that $id you can do a single SELECT statement and retrieve those $limitstart and $catid from the #__rsgallery2_files table..
And what is gained using id in URL instead of catid, limitstart, and page? Well, if you think about it a bit, you'll see that your links for displaying a certain image, remain the same no matter if user changes ordering of image in a gallery, or if the user moves the image in another gallery. That way you will be able to get the sef extensions written by other people in your email inbox, to save your time, but this way, there is no way to create good SEF links if your links to a certain image change a lot, depending on the user actions on that image..
On your forums, I've read nothing but blaming other people, like developers of all those SEF components, for not updating their extension list with one for RSGallery.. This could really be a big problem for this component.
Also, the developers of this component are also responsible for keeping their content elements files (for JoomFish), the same reason as above..
Oh yes, I almost forgotten another very important thing. While I was trying to somehow develop the SEF extension for myself (since no extensions found on the internet were good enough for me) I've realized you are using $catid and $limitstart variables (altogether with page=inline) to display a singe image. Is this really necessairy? For example, you could use only $id (like for download link) and from that $id you can do a single SELECT statement and retrieve those $limitstart and $catid from the #__rsgallery2_files table..
And what is gained using id in URL instead of catid, limitstart, and page? Well, if you think about it a bit, you'll see that your links for displaying a certain image, remain the same no matter if user changes ordering of image in a gallery, or if the user moves the image in another gallery. That way you will be able to get the sef extensions written by other people in your email inbox, to save your time, but this way, there is no way to create good SEF links if your links to a certain image change a lot, depending on the user actions on that image..
byburek, August 22, 2007

