Quote:
ghia wrote:
I think they all will run or have a compatible version.
You can try it out on a local server with eg XAMPP.
Thanks for that link, very useful and interesting site. I'm running Linux/Ubuntu now locally, so technically I could add Apache and MySQL fairly easily. That said, I might just add a seperate path on current site to install it all 'afresh', from memory it's only a few path names then to change, to move it all to current 'home' path.
Quote:
bjuti wrote:
Liaise work, but try xForms fork (it can import from Liaise)
Update SmartObject and SmartSection (actual is 2.14 or try Publisher fork in alpha stage, also can import from SS)
Downloaded xForms, it has no readme or such and a few EXE and INI files, looks kinda 'windo-ish' to me. But will try it out. Liaise doesn't do any captcha, so I do get some spam from it now.
Will be nice to drop SmartObject and Smartsection, in place of Publisher. I see there is no archive for Publisher, will just do a wget recursive to grab those files. Hopefully, it is stable. I didn't think much of Smartfactory moving away from XOOPS, so will be nice to drop Smartsection.
Quote:
Burning wrote:
Lastest versions :
• Liaise - 1.26 --> xForms 1.01
• protector - 3.4 --> ok. There is a beta version Protector 3.50
• Site Map - 1.30 --> ok. There is also an enchancement by Tank55
• Smartobject - 0.9 --> don't know
• Smartsection - 2.13 --> Smartsection 2.14. But you should use Publisher as already said before
• Wflinks - 1.03C --> WF-Links 1.08
• Xhld0 - 3.07 --> XHLD 3.08
Thanks for all those links. I had a quick look at 2..4.4 , and it seems Protector is already included in XOOPS core, so now no need to get the module I assume. That said, it would be prudent to keep to the latest version. I'm assuming the Protector in XOOPS core is no different from the 'same version' of Protector, as a single module.
Fairly sure Smartobject was only needed because of Smartsection, so if I go to Publisher, then I can drop Smartobject as well.
I have always had to modify XOOPS userinfo.php as follows (lines added between
//BEGIN and
//END statements)
$xoopsOption['pagetype'] = 'user';
include 'mainfile.php';
include_once XOOPS_ROOT_PATH.'/class/module.textsanitizer.php';
//BEGIN - 20070412.1 - mod to stop guests from viewing registered user profiles
$xoopsUser or redirect_header('index.php', 3, _NOPERM);
//END - 20070412.1 - mod to stop guests from viewing registered user profiles
include_once XOOPS_ROOT_PATH . '/modules/system/constants.php';
This was always added, because I never liked the fact that a guest user could do this:
http://www.example.com/userinfo.php?uid=1and find out the username of 'admin' ; not real good for security. Hopefully XOOPS has come a bit further now, in that respect, and there would be no need for that mod.
Thanks to all for your replies,
Pete