12
Right, I apologise for bringing this up again, and I know it's scheduled for a future release...
But Search Engine Friendly URLS in XOOPS - is there any chance this feature can be brought forward and added ASAP?
XOOPS is my preferred CMS, I *want* to use XOOPS, but while I am now getting to do more sites for other people, I find I cannot use it due to the lack of this feature (you'd be surprised how important this is, especially commercial sites), and as a result I am having to use Joomla.
I know I am nagging, but I really think this is something that is making people pass up XOOPS in favour of CMS' like Joomla or even Wordpress.
But Search Engine Friendly URLS in XOOPS - is there any chance this feature can be brought forward and added ASAP?
XOOPS is my preferred CMS, I *want* to use XOOPS, but while I am now getting to do more sites for other people, I find I cannot use it due to the lack of this feature (you'd be surprised how important this is, especially commercial sites), and as a result I am having to use Joomla.
I know I am nagging, but I really think this is something that is making people pass up XOOPS in favour of CMS' like Joomla or even Wordpress.
13
XOOPS' lack of URL rewriting/SEO URLs is a major stumbling block for it to be honest.
Without spending hours checking, I believe XOOPS (and its clones) is the *only* CMS without this feature. It seriously means that I cannot use it in a commercial environment. At least not without hours of work hacking about with code.
It doesn't seem like much, but it's that one feature that is letting it down, and people expect this with their sites these days.
However, as for URL rewriting in Joomla - it is there, but it is still at times hit and miss. Even in some articles, it might just display the article ID and not the stub/alias. Then if you set up a menu link to an article, the current rewritten link breaks, and vice versa.
I've not tried any comment modules in Joomla, so I don't know how they compare - but again, I don't think there's anything wrong with the comment system in XOOPS, which seems to work well.
Without spending hours checking, I believe XOOPS (and its clones) is the *only* CMS without this feature. It seriously means that I cannot use it in a commercial environment. At least not without hours of work hacking about with code.
It doesn't seem like much, but it's that one feature that is letting it down, and people expect this with their sites these days.
However, as for URL rewriting in Joomla - it is there, but it is still at times hit and miss. Even in some articles, it might just display the article ID and not the stub/alias. Then if you set up a menu link to an article, the current rewritten link breaks, and vice versa.
I've not tried any comment modules in Joomla, so I don't know how they compare - but again, I don't think there's anything wrong with the comment system in XOOPS, which seems to work well.
14
I've recently taken over a site built with Joomla, and all I can say is that I bloody well hate it. With a passion.
Unfortunately, I can't rebuild it with someone else, and to make matters worse, I'm now having to write a plugin.
It does have some nice features, but gnnn...
Unfortunately, I can't rebuild it with someone else, and to make matters worse, I'm now having to write a plugin.
It does have some nice features, but gnnn...
15
I know Simple XOOPS is supposed to be integrated into XOOPS at some point, along with SEO friendly URL support.
The thing is, I want to make sure this will be supported in my future modules, so what is the best way of building and presenting URLs?
By that, I mean - either build the URL in the code and send a variable like "$url" through to the template, or send the individual parts to the template and put it together there? I suspect the former, but having no idea how this will be implemented, I would just try and save myself hassle later on.
The thing is, I want to make sure this will be supported in my future modules, so what is the best way of building and presenting URLs?
By that, I mean - either build the URL in the code and send a variable like "$url" through to the template, or send the individual parts to the template and put it together there? I suspect the former, but having no idea how this will be implemented, I would just try and save myself hassle later on.
16
The latter one seems to work OK as well.
The only thing that lets them down at present is the lack of an admin/database back-end.
The only thing that lets them down at present is the lack of an admin/database back-end.
17
Quote:
I meant to say in my last reply - the point of this book is to at least get a decent reference for module developers.
The other books are general XOOPS books, based on setting it up and customising. I don't know how far any of them go into writing modules as I've not read them. They are also 2 years old now, so are getting outdated.
jezjones24 wrote:
Although i think the code is good, i would not use XOOPS for future projects where i had a choice, purely down to the difficulty in finding useful documentation. Another book would only add to the mess.
I meant to say in my last reply - the point of this book is to at least get a decent reference for module developers.
The other books are general XOOPS books, based on setting it up and customising. I don't know how far any of them go into writing modules as I've not read them. They are also 2 years old now, so are getting outdated.
18
Quote:
This isn't a dig, but I would like to try and keep XOOPS politics out of this thread. Although I can see what you mean, the XOOPS project has pulled back together recently, and is moving on again.
Now, as for versions (I meant to say about this in my original post) - depending upon when XOOPS version 3 is released, I would prefer to base it on that. If not, it will written v2.3 and later only.
This book will be fairly targeted - where it will go into DBs, templates and PHP for example, it will assume that you will know something about those topics, or have other, more specific books on them.
jezjones24 wrote:
I have developed a number of modules for our implementation of Xoops, these are not released as they are not generic, nor used online (its an intranet).
However to answer your first question, No, i would not buy a book on a project such as xoops. There is already XOOPS books but based on the fragmented and difficult to find documentation, i would expect too much from a book and i would expect it to cover many versions of xoops.
Also i am a little concerned about the XOOPS project, as not only is the docs fragmented, there seems to be alot of fragmentation in the project itself.
Although i think the code is good, i would not use XOOPS for future projects where i had a choice, purely down to the difficulty in finding useful documentation. Another book would only add to the mess.
This isn't a dig, but I would like to try and keep XOOPS politics out of this thread. Although I can see what you mean, the XOOPS project has pulled back together recently, and is moving on again.
Now, as for versions (I meant to say about this in my original post) - depending upon when XOOPS version 3 is released, I would prefer to base it on that. If not, it will written v2.3 and later only.
This book will be fairly targeted - where it will go into DBs, templates and PHP for example, it will assume that you will know something about those topics, or have other, more specific books on them.
19
I've become a little frustrated by the lack of and/or fragmented info on writing modules for XOOPS. I'm also a bit crap at reverse engineering stuff from other modules - it's time consuming and perhaps a little unfair on the people who've done it.
So, I think it's perhaps time to write a "how to create a XOOPS module" book, and I am willing to try and attempt this challenge.
I have some questions/points to put to you:
1) Does anyone know of such a project already going ahead?
2) Would *you* buy such a book, especially if it meant you got to find out about some handy API stuff?
Uhm, yeah. so. I am not the world's best PHP coder, nor do I know XOOPS inside and out as well as other people - this means that I will need help from other developers, both XOOPS core coders, main module developers and the average person out there.
I would be the main author, and will do the bulk of the writing and compiling of info, code, screen shots and so on. I am also willing to have co-authors on this project.
This will be a paper product, and so if it is accepted for publishing, will be sold in Real Life(tm) and on-line shops, etc. Royalties from this will go to me, co-authors and a percentage will be donated to the XOOPS project.
I don't know how much this book would "earn" for me, I suspect it won't be a great deal as it's a relatively small market. The real idea however, is to help try and encourage coders to take up and write more (hopefully, quality) modules for XOOPS.
If you're interested in helping, please get in touch privately - and perhaps with suggestions of people I should contact to get involved. Please let me have your name and an e-mail address if you want to go on the mailing list (which will be set up if there's enough demand).
So, I think it's perhaps time to write a "how to create a XOOPS module" book, and I am willing to try and attempt this challenge.
I have some questions/points to put to you:
1) Does anyone know of such a project already going ahead?
2) Would *you* buy such a book, especially if it meant you got to find out about some handy API stuff?
Uhm, yeah. so. I am not the world's best PHP coder, nor do I know XOOPS inside and out as well as other people - this means that I will need help from other developers, both XOOPS core coders, main module developers and the average person out there.
I would be the main author, and will do the bulk of the writing and compiling of info, code, screen shots and so on. I am also willing to have co-authors on this project.
This will be a paper product, and so if it is accepted for publishing, will be sold in Real Life(tm) and on-line shops, etc. Royalties from this will go to me, co-authors and a percentage will be donated to the XOOPS project.
I don't know how much this book would "earn" for me, I suspect it won't be a great deal as it's a relatively small market. The real idea however, is to help try and encourage coders to take up and write more (hopefully, quality) modules for XOOPS.
If you're interested in helping, please get in touch privately - and perhaps with suggestions of people I should contact to get involved. Please let me have your name and an e-mail address if you want to go on the mailing list (which will be set up if there's enough demand).
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|