21
cadelite
SEO vs XOOPS
  • 2012/2/5 8:40

  • cadelite

  • Just popping in

  • Posts: 86

  • Since: 2008/1/15


Will there be any SEO related improvements in XOOPS 2.6?

Quoted from Wikipedia (http://en.wikipedia.org/wiki/XOOPS )

"However, XOOPS does not give its users full control over their URLs. Where URL rewriting is possible, XOOPS often uses redirects that may confuse search engines. In addition, some XOOPS modules create duplicate content by making the same information available on more than one URL while in other cases (especially in case of multilingual sites), several sets of content may be made available through the same URL."

It seems that XOOPS still requires a lot of "additional works" inside its core system and basic files in making it SEO-friendly. It is hoped that XOOPS will add more SEO-friendly features inside its core (without the need to rely on its modules) to win those other CMS like Wordpress, Joomla, Drupal, etc.

By the way, will XOOPS 2.6 remove all obsolete and deprecated classes and functions and shrink the size of core system?

Thank you all for your great effort in development! Bravo!!



Regards,

cadelite



22
cadelite
Re: XOOPS 2.5.4 and XOOPS 2.6.0 release together?
  • 2011/10/24 10:33

  • cadelite

  • Just popping in

  • Posts: 86

  • Since: 2008/1/15


Quote:

redheadedrod wrote:

This definitely sounds like a great move forward. The code as is now can be very difficult to review and learn.


Maybe a 200% code refactoring on XOOPS project is a must to the further development of XOOPS.

Drupal lifts the burden of backward compatibility. Every version has great features added and forgets the backward compatibility to the previous versions.

See if XOOPS will follow it. Of course, it may cause many users who are still using XOOPS 2.3 or earlier version, like those in Taiwan and Japan, to make a really hard decision on whether or not upgrading their websites to the latest version of XOOPS.



23
cadelite
Re: XOOPS 2.5.4 and XOOPS 2.6.0 release together?
  • 2011/10/23 17:05

  • cadelite

  • Just popping in

  • Posts: 86

  • Since: 2008/1/15


Thank you, trabis!

I believe that XOOPS 2.6.0 is worthwhile to wait (especially it marks a brighter era for XOOPS).

Having been using XOOPS for over 3 years, I think XOOPS is very good at building community and commercial websites, except that the size of files included in XOOPS is really too large compared to Drupal and Wordpress. Maybe owing to maintaining the backward compatibility and the obsolete codes included in the old trunks.

I hope the future versions of XOOPS (2.6.0 or later) will use more advanced features of PHP 5.3 or later and, if possible, will add more support for PostgreSQL and MS SQL Server.

Not sure if the recent popular NoSQL databases are suitable for the future XOOPS development but I believe that there will be a chance for XOOPS to be used in one of the most popular social websites in the world. Let's see!

Thank you very much! You XOOPS developers are the most respectable and you worth the praises from us, as XOOPS users. Thank you!! :)



Regards,

cadelite



24
cadelite
XOOPS 2.5.4 and XOOPS 2.6.0 release together?
  • 2011/10/23 2:32

  • cadelite

  • Just popping in

  • Posts: 86

  • Since: 2008/1/15


Just out of curiosity!


Will XOOPS 2.5.4 RC and XOOPS 2.6.0 Beta release together since both of them are updated frequently in SVN?


Thank you very much for all the efforts of XOOPS developers. XOOPS is a wonderful masterpiece indeed.


Thanks a lot!




Regards,

cadelite



25
cadelite
Re: Is XOOPS 2.5.2 going to be released?
  • 2011/9/13 5:08

  • cadelite

  • Just popping in

  • Posts: 86

  • Since: 2008/1/15


Thanks, Mamba!

XOOPS 2.5.1 Final is released on 8 Apr 2011, five months ago. Time passed so fast!

Is XOOPS Engine (or XOOPS 3.0) still a future path to XOOPS?

Or is it now a separate fork other than XOOPS, just like ImprXXXCMS?

If XOOPS Engine is no longer a future version of XOOPS, XOOPS 2.6 should be the current future path of XOOPS, being backward compatible to XOOPS 2.5.X. Right?

Thanks a lot!

For bug fixing, your developers are much more competent than us as we just customize CMS and modules for clients, instead of creating ones. Thank you all for your efforts in XOOPS development!!



Best regards,

cadelite





26
cadelite
Is XOOPS 2.5.2 going to be released?
  • 2011/9/12 13:22

  • cadelite

  • Just popping in

  • Posts: 86

  • Since: 2008/1/15


Is XOOPS 2.5.2 going to be released in this week? or at the end of Sep 2011?

Any planned release date for XOOPS 2.6?

Thanks a lot!

Much thanks to all developers for XOOPS, a brilliant CMS!!



27
cadelite
Re: 2011 Sitemap Module
  • 2011/4/18 8:02

  • cadelite

  • Just popping in

  • Posts: 86

  • Since: 2008/1/15


Quote:
OK, it's done - you can download it for testing from SourceForge

I might do it for the regular "SiteMap", but this will be a little but harder because it uses the D3 GUI. Is there actually any interest in doing this?


Mamba, Thank you very much!

I've used your xSitemap module in one of my sites. Besides, I added more graphics and images to the sitemap and modified the xml structure of the sitemap to make it look more professional, suiting my client's taste.

I do suggest to incorporate it into XOOPS 2.5.2 and later as a core part since XOOPS is a beyond-Web 2.0 stuff and building XML sitemap should be a must for the later versions.

Thank you all indeed!!



28
cadelite
2011 Sitemap Module
  • 2011/2/27 7:12

  • cadelite

  • Just popping in

  • Posts: 86

  • Since: 2008/1/15


Would any of you recommend a module for showing sitemaps of a website using XOOPS 2.5.0 Final?

I want one that can generate human-being reading sitemap and xml style sitemap for the purpose of Google, Yahoo! and other search engines.

I have found "sitemap 1.31" written by Peak XOOPS but it was released on 5 Dec 2008, long before the release of XOOPS 2.5.0 Final. I doubt if it have any compatibility issue and if it can generate the xml style sitemap fed to Google, Yahoo! and other search engines. Even though, after searching xoops.org, I found that the most popular sitemap module is this one, I hope there will be an updated module for sitemap used in 2011 satifying SEO and other criteria.

Thank you very much.


Best regards,

cadelite



29
cadelite
Re: Legal Quotations of GPL and Rights
  • 2010/7/7 7:31

  • cadelite

  • Just popping in

  • Posts: 86

  • Since: 2008/1/15


Thanks, Mamba!

For those software released under GPL, the traditional profit-making method of keeping source code in pyramids and securing it from outsiders' eyes does not work. Instead, the competition (and, at the same time, co-operation) by techniques and skills in software development becomes a key and new method of profit making. On top of these, the developers may also provide counselling, training and after-sale services to the end users (e.g. the successful mode of XOOPS in Taiwan ).

Why not just allow your end users to modify or edit their source code to suit their own uses or fix the source code by themselves (or counselling you, instead). If your software is really brilliant and loved by the end users, it will be popular and you will still be making profit. Don't get used to the bad practice of the developer of printer driver (the open source story) !

Let's put our efforts on the development of XOOPS 2.5 and 3!



30
cadelite
Re: What a ranker!
  • 2010/7/7 4:12

  • cadelite

  • Just popping in

  • Posts: 86

  • Since: 2008/1/15


Put it simple.

For paid or commerical modules, the user of the module is required to pay a certain amount/fee (either monthly, yearly or in a lump sum) to the module author for the use of module. In return, the module author grants a right to the user to use the module in his/her XOOPS module. In the same time, under GPL, the module author must give the source code of the paid or commerical module to the user for him/her to modify it in case the module has problems or the user wants to adapt it to other purpose.

However, if the paid or commerical module is completely independent. It means that it can run without the installation of XOOPS or other CMS. Then, it may follow its own licence and may choose not to give the source code of the module to the user even though the user has paid the author an amount as consideration.

However, back to reality, if the author of a commerical or paid module DOES prohibit the user (after he/she paid a fee/amount) from having the source code of the module and from modifying, editing or releasing the source code:

(1) What will XOOPS do? What will other authority do?
(2) What loss (economic, social or legal loss) to the author?
(3) What penalty/compensation will the author suffer from?

If there is no harm or loss to the author of these paid or commerical modules, the user of these paid or commerical modules may not be affected. However, if (1) - (3) is possible, the user of the these commerical or paid modules will be affected and may be prohibited from continuing to use these modules in their XOOPS site.

All the above are my opinion and understanding. If anything above is incorrect, please correct it. Thanks!




TopTop
« 1 2 (3) 4 5 6 ... 8 »



Login

Who's Online

165 user(s) are online (115 user(s) are browsing Support Forums)


Members: 0


Guests: 165


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Mar 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits