HI was just wondering, I want to install another more upto date module for adding content to replace Tiny Content and was wondering if Pico/TinyD would conflict with my TinyContent module since TinyD was created using the code from TinyContent.
I want to be able to keep Tiny Content on while I transfer the content over.
Thanks in advance.
hi bdw.
Tiny"Content" ?
Don't you know the fatal vulnerability of TinyContent?
Anyway, since pico is a full-scratched module, you can install pico freely with TinyD/TinyContent.
If you use the core 2.0.14/15/16 from xoops.org, fix the bug.
If you want to use TinyD, just overwrite TinyContent and update the module.
And don't forget removing spaw under tinycontent.
Quote:
since TinyD was created using the code from TinyContent.
Do you really think so?
TinyD scarcely uses the code from TinyContent.
If you can, compair them.
yeah, i know theres a vulnerability. That coupled with the fact it hasnt been updated in so long has made me want to change module.
BTW, wot bug do i have to fix? Please explain in detail as ive tried a search of xoops and havent found anything.
BTW, I just assumed TinyD was a newer verion of TinyContent. Soz, my bad.
Quote:
BTW, wot bug do i have to fix? Please explain in detail as ive tried a search of xoops and havent found anything.
If you mean BUG of xoops core, refer OneOfTen's post
[1.1.1.1]Else if you mean the vulnerability of TinyContent, remove spaw under TinyContent right now.
It makes the fatal (sudden-death) vulnerability away.
But there are some moderate critical vulnerabilities in TinyConennt.
(CSRF, XSS etc.)
Thus, I almost remove the codes from TinyContent.
Quote:
BTW, I just assumed TinyD was a newer verion of TinyContent. Soz, my bad.
TinyD can be said as a newer version of TinyContent.
Just overwite TinyContent by TinyD. (Then update the module)
TinyD will work fine.