162
In XOOPS2, you can turn this security check off very easily by modifying the following code in include/common.php on line 51:
define('XOOPS_DB_CHKREF', 1);
to
define('XOOPS_DB_CHKREF', 0);
However, we do not recommend turning this off unless you are able to definitely trust the visitors coming to your site.
define('XOOPS_DB_CHKREF', 1);
to
define('XOOPS_DB_CHKREF', 0);
However, we do not recommend turning this off unless you are able to definitely trust the visitors coming to your site.
164
It depends on how the original date was stored in DB. In XOOPS, all date related data are stored as timestamp generated by php time() function.
165
Yes, I am currently working on the ratings feature for the core.. and should be easily reuseable among modules
166
Yes, sorry but the CVS codes currently do not work, but they are there for the developers to see what have been changed. We will be updating the codes in a very short time.
167
strict: a-z, A-Z, 0-9 only
medium: strict plus <>,.$%#@!'"
loose: medium plus ?{}[]()^&*`~;:\+=
Currently, no spaces are allowed in a user name
medium: strict plus <>,.$%#@!'"
loose: medium plus ?{}[]()^&*`~;:\+=
Currently, no spaces are allowed in a user name
169
No, there still will be no standardized browser sniffing codes in XOOPS2, but only in some parts we try to detect if the client is using IE or not before adding some IE specific http header variables.
I see that those links you've suggested are all javascript codes, so include/xoopsjs.php might be the right file to include the codes, if you need to do a site-wide sniffing.
You can also consider using native PHP functions like get_browser() or simply looking at the values of $HTTP_USER_CLIENT the client sends to the server.
By the way, I have come into the following script when I was searching for a good php sniffer script some time ago, and it looked very good.
phpClientSniffer
I see that those links you've suggested are all javascript codes, so include/xoopsjs.php might be the right file to include the codes, if you need to do a site-wide sniffing.
You can also consider using native PHP functions like get_browser() or simply looking at the values of $HTTP_USER_CLIENT the client sends to the server.
By the way, I have come into the following script when I was searching for a good php sniffer script some time ago, and it looked very good.
phpClientSniffer
170
Yes, I like your idea about passing an object as the parameter of theme functions. However, in XOOPS2, there will be no theme functions at all, but all the values for presentation are assigned to template variables via the Smarty global object like $smarty->assign('name', $value);.
Yes, the old themes will still work fine in XOOPS2, but since the Smarty template system will be the primary theme system we will be using, it is unlikely that we will be doing any modifications on the current theme system.
Yes, the old themes will still work fine in XOOPS2, but since the Smarty template system will be the primary theme system we will be using, it is unlikely that we will be doing any modifications on the current theme system.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|