5894
So they are skipping right over PHP6?
Richard has been doing some mad coding lately... Lots of new updates...
Richard has been doing some mad coding lately... Lots of new updates...
5895
Yes, there are still some bugs
Taking the test, if I create tables with a few fields, saves them regularly, but if I create with many fields saves only the basis of the fields.
However, I added other code and this definitely makes mistakes
Taking the test, if I create tables with a few fields, saves them regularly, but if I create with many fields saves only the basis of the fields.
However, I added other code and this definitely makes mistakes
5896
In case you didn't hear yet - PHP 7 is coming soon (release planned for October), and it will provide a major performance improvements, in many cases up to 100% 
You can read more in this "Info World" article
As mentioned in another article, the performance improvements are very impressive:
Quote:
Of course, XOOPS users will be asking: "What about us? Will XOOPS run on PHP 7?"
Absolutely!
As you might remember, XOOPS was one of the first major CMS solutions that was certified for PHP 5.5, and the current version runs without any problems on PHP 5.6. And as the creator of PHP said recently, as it was quoted in the first article:
Quote:
Since XOOPS runs cleanly under PHP 5.6.8 on my PC, our users will have no problems. But Richard, our Core Team leader, is already looking at PHP 7, to fully certify the upcoming XOOPS 2.6.0 for PHP 7. The XOOPS Team, as always, is fully committed to maintain XOOPS up to date with latest PHP developments, so you as our users, can be assured that with XOOPS there is always a solid migration path for you into the future!
FYI: the future XOOPS versions will have PHP 5.4 as the minimum requirement.
You can read more in this "Info World" article
As mentioned in another article, the performance improvements are very impressive:
Quote:
For example, the PHP team ran the WordPress CMS on phpng, and it resulted in a drop from 27 seconds to 18 seconds for 100 requests. The number of machine instructions went from 9.4 billion down to 4.99 billion. "This is a real-world app running real-world PHP and starting to see very dramatic improvements," Gutmans said
Of course, XOOPS users will be asking: "What about us? Will XOOPS run on PHP 7?"
Absolutely!
As you might remember, XOOPS was one of the first major CMS solutions that was certified for PHP 5.5, and the current version runs without any problems on PHP 5.6. And as the creator of PHP said recently, as it was quoted in the first article:
Quote:
"Lerdorf also warned that the upgrade also deprecates some PHP 4 functions: "Chances are pretty good if your code is from 12 years ago, it will probably break under PHP 7. If it works under PHP 5, you should be fine."
Since XOOPS runs cleanly under PHP 5.6.8 on my PC, our users will have no problems. But Richard, our Core Team leader, is already looking at PHP 7, to fully certify the upcoming XOOPS 2.6.0 for PHP 7. The XOOPS Team, as always, is fully committed to maintain XOOPS up to date with latest PHP developments, so you as our users, can be assured that with XOOPS there is always a solid migration path for you into the future!
FYI: the future XOOPS versions will have PHP 5.4 as the minimum requirement.
5899
I've been working for a while on a project of mine, and during that I gazed through the obituaries templates of xBootstrap.
What I noticed is that there is a lot of directly applied/inline styling that has been applied, making it impossible to override it with CSS files. An example of this can be found on https://github.com/angelorocha/xbootstrap/blob/master/modules/obituaries/obituaries_users.html.
Here you can see several things:
* Inline the following rules are being made, which should be removed (.heyula shouldn't be there, should be something like .obituaries):
* On https://github.com/angelorocha/xbootstrap/blob/master/modules/obituaries/obituaries_user.html there is an extreme lot of direct inline styling.
I'll try to submit an update for this once I find the time (I'm currently moving, so really busy time for me). :)
What I noticed is that there is a lot of directly applied/inline styling that has been applied, making it impossible to override it with CSS files. An example of this can be found on https://github.com/angelorocha/xbootstrap/blob/master/modules/obituaries/obituaries_users.html.
Here you can see several things:
* Inline the following rules are being made, which should be removed (.heyula shouldn't be there, should be something like .obituaries):
<style type="text/css"> .heyula { list-style: none; margin: 0; padding: 0; } .heyula li {width: 10%; float: left;} style> * On https://github.com/angelorocha/xbootstrap/blob/master/modules/obituaries/obituaries_user.html there is an extreme lot of direct inline styling.
I'll try to submit an update for this once I find the time (I'm currently moving, so really busy time for me). :)
5900
This is way of having a signup sentry on your XOOPS 2.5 site these are the following files:-
/modules/systems/preloads/sentry.php
/language/english/mail_template/deletion.tpl
/modules/systems/preloads/sentry.php
/**
* System Preloads
*
* You may not change or alter any portion of this comment or credits
* of supporting developers from this source code or any supporting source code
* which is considered copyrighted (c) material of the original comment or credit authors.
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
*
* @copyright The XOOPS Project http://sourceforge.net/projects/xoops/
* @license GNU GPL 2 (http://www.gnu.org/licenses/old-licenses/gpl-2.0.html)
* @author Simon Roberts (AKA +61405130385)
* @version $Id: xortify.php 8066 2011-11-06 05:09:33Z beckmi $
*/
defined('XOOPS_ROOT_PATH') or die('Restricted access');
class SystemSentryPreload extends XoopsPreloadItem
{
function eventCoreFooterEnd($args)
{
$criteriaAvarta = new Criteria('user_avarta', '%blank.gif%', 'LIKE');
$criteriaNewReg = new CriteriaCompo(new Criteria('user_regdate', time() - 2 * 24 * 3600, '<='));
$criteriaNewReg->add(new Criteria('last_login', 0));
$criteriaIdle = new CriteriaCompo(new Criteria('last_login', time() - 24 * 7 *4 * 24 * 3600, '<'));
$criteriaIdle->add(new Criteria('last_login', 0, '<>'));
$criteriaFirst = new CriteriaCompo($criteriaAvarta);
$criteriaFirst->add($criteriaNewReg);
$criteria = new CriteriaCompo($criteriaFirst);
$criteria->add($criteriaIdle, "OR");
$user_handler = xoops_gethandler('user');
$tokill = array();
foreach($user_handler->getObjects($criteria, true) as $key => $user)
{
if (!$user->isAdmin() && in_array(XOOPS_GROUP_USER, $user->getGroups()))
$tokill[$user->getVar("uid")] = $tokill;
}
if (!empty($tokill))
{
xoops_loadLanguage('user');
$xoopsMailer =& xoops_getMailer();
$xoopsMailer->useMail();
$xoopsMailer->setTemplate('deletion.tpl');
$xoopsMailer->setSubject(sprintf("Your account on '%s' has been deleted by the sentry!", $xoopsConfig['sitename']));
$xoopsMailer->setToUsers($tokill);
@$xoopsMailer->send();
$GLOBALS["xoopsDB"]->queryF("DELETE FROM `" . $GLOBALS["xoopsDB"]->prefix('users') . "` WHERE UID IN(" . implode(", ", array_keys($tokill)) . ")");
$GLOBALS["xoopsDB"]->queryF("DELETE FROM `" . $GLOBALS["xoopsDB"]->prefix('groups_users_link') . "` WHERE UID IN(" . implode(", ", array_keys($tokill)) . ")");
}
}
}
?> /language/english/mail_template/deletion.tpl
Your account "{X_UNAME}" at {SITENAME} has been deleted automatically by our sentry.
This is because you either creating the account have not changed your avarta within
2 days or you have not logged-on within 24 months!
You can not login anymore and you account is no longer active.
-----------
{SITENAME} ({SITEURL})
webmaster
{ADMINMAIL} 
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|