Version: 2.0.15
File: class/xoopsform/form.php
Line#: 193

Old code:


New code:


This will fix above error "Call to a member function on a non-object..."

Enjoy. Someone with commit access please change this in 2.0.15 code base.

Thanks.

All SmartXXX modules are brought to you by SmartFactory Check on their homepage -http://smartfactory.ca/

Next release should have it. If you want to try now, get CVS version.

Thanks.

Guys,

I just completed coding the SEO feature for my favorite SmartSection module. The changes are committed on HEAD, so wait till next release. Stay tuned....

Feature preview...

Originally URLs generated from modules are something like these:

http://localhost/modules/smartsection/category.php?categoryid=3
http://localhost/modules/smartsection/item.php?itemid=1
http://localhost/modules/smartsection/print.php?itemid=2

These parameterized URL are not very effective in getting good search rank for various reasons. So I did this hack to make these URLs look like

Using mod_rewrite

http://localhost/smartsection.category.3/yahoo-mail.html
http://localhost/smartsection.item.1/how-is-yahoo-mail-different-from-email.html
http://localhost/smartsection.print.2/can-i-turn-the-ads-off.html

Using PATH_INFO

http://localhost/modules/smartsection/seo.php/category.3/yahoo-mail.html
http://localhost/modules/smartsection/seo.php/item.1/how-is-yahoo-mail-different-from-email.html
http://localhost/modules/smartsection/seo.php/print.2/can-i-turn-the-ads-off.html

Above rewrite prints many keywords (from title) in URL itself. Google started caching each and every page when I turned on SEO. When searched for related keywords; this new URL will increase the search-rank.

You mean, something likehttp://merabhopal.com ?

It's a custom HTML block placed in right column. Very simple stuff. I would also suggest to configure cache for this block - may be a week.

submitter int(11) unsigned NOT NULL default '0'

link owner info is captured in DB so it is very much do-able without making huge changes.

XOOPS certified modules...

Can we discuss about a QA process for un-official modules as well?

People blame Microsoft for making a very insecure and unstable OS. In reality, OS itself is pretty stable (NT family kernel was designed by same person who designed Digital-UNIX). The operating system is well designed and has great support for muti-threading and other basic stuffs; still it is one of most unstable OS.

The real problem with Microsoft is that they exposed very powerful APIs but had no control (until recently) over how other vendors were using them. Most of the problems were in device-drivers; bringing down the server. Starting from Windows XP, Microsoft finally started driver-certification process which is pretty successful. As a result Windows XP (and family) became much more stable than.

Moral of story is:

Xoops core team should also take responsibility of mentoring and reviewing all XOOPS module development effort. When someone says that his XOOPS site is slow, that is mostly because he is experiencing some in-efficient module. But ironically, this blame mostly goes to Xoops.

In my free time I sometime walk through XOOPS core; and many times I reported any possibilities of improvement via Sourceforge tracker. As a whole my feedback for XOOPS core and official modules is pretty good. Good work team !!!

Many third party modules are also very well written. I appreciate all of their efforts in making this open source project successful. Can we put some effort to improve quality of whole community, not just XOOPS core? 'XOOPS Module Development Forge' is a great effort in this line but what about QA and code-review?

Please discuss it for welfare of whole XOOPS community.

You may want to check downgrade script

http://x22.pzcci.org/files/x223-222-downgrade.tar.gz

Also check comments on this article -https://xoops.org/modules/news/article.php?storyid=2533

Google indexed all of my SEO page very quickly Check this I also see google-page-rank of 2 just in few days.

I also added code to make link or category title appears in page title