its a minor bug, the "List All Articles" has its link pointing from base directory instead of XOOPS home directory

example
List all articles has the following link
http://127.0.0.1/modules/wfsection/viewarticles.php?category=1

where as the link should be same as the category link
http://127.0.0.1/xoops/html/modules/wfsection/viewarticles.php?category=1

here xoops/html is the folder setup in which XOOPS installed.

if i click on the category (section) the second link (http://127.0.0.1/xoops/html/modules/wfsection/viewarticles.php?category=1) is there which is working fine, but when clicking the List all articles ... it breaks down.

Might be bug in template or somewhere...

***********************************
Edit
***********************************

on a quick look found that following code in wfsection_catindex.html is not working as expected. looks like here $xoopsurl is not getting its value.

<div align="right"><a href='<{$xoopsurl}>/modules/wfsection/viewarticles.php?category=<{$category.catid}>'><small><img src="images/icon/arrow_blueW.gif" alt="" width="16" height="16" border="0" align="absmiddle"> <{$lang_listarticles}></small></a></div>
<br />

Any one knows what could be the reason

vinit

@Vinit:

This is a known bug and you will find the anser to you question here:
Answer Here

Other Known Issues Reported

Liquid

Added to the WFSections Bug report section here

Edit: Whoops Sorry Liquid - missed that one! *blush*

Thanks, trying to implement that change.. i think is very minor bug. please fix it in your side too.

Converting $xoopsurl to $xoops_url didnt work :( still showing same link. Any other thing need to be checked ????

Vinit

This and the other bugs in the afforementioned thread will be fixed in the next release.

Please update your module in System Administration. After that it should be working as expected.

You might also check here:

View All Articles

Quote:

Did you update the module after the changes?

Liquid

Sorry to bust in like this but, is there an upgrade to this version of WFS? I using 1.01


If not I may have to start learning PHP and MySSQL and build my own.

ps.. see I cant even spell MySQL propelly

Quote:

Oh, i forgot to do that. :( well will do that and see if it works.

======
EDIT
======

Did module update, still facing the same problem ????

Anything missing somewhere ??