152
Quote:
The "Main Menu" phase is defined there, but changing it there won't do anything once the system is installed.
The block definitions for the system module are created during the initial install. The constants are used to set the default name when the row for the block in the newblocks table is first created. From that point on, to change it, you must edit that block in the admin area.
The block name is always just as it is set in the block editor. To make them multilingual, you can use xlanguage and use language tags in the name.
In days past, the local support sites often offered a XOOPS install kit with the local language files already added. That approach localized everything for a single language system in the initial install.
For the record, this is one of many localization issues that will be fixed in the next generation of XOOPS.
Zap_English wrote:
... is not correct. It still shows on the side as "Main Menu" even though it's been changed in that file to "Главное меню"
The "Main Menu" phase is defined there, but changing it there won't do anything once the system is installed.
The block definitions for the system module are created during the initial install. The constants are used to set the default name when the row for the block in the newblocks table is first created. From that point on, to change it, you must edit that block in the admin area.
The block name is always just as it is set in the block editor. To make them multilingual, you can use xlanguage and use language tags in the name.
In days past, the local support sites often offered a XOOPS install kit with the local language files already added. That approach localized everything for a single language system in the initial install.
For the record, this is one of many localization issues that will be fixed in the next generation of XOOPS.
153
For the record, 2.5.8 was extensively tested on multiple Linux variants as well as multiple stacks on Windows. Somehow, you are skipping the autoloader if Xmf\IPAddress can't be found. The autoloader is started when class/xoopsload.php is included.
For the database transactions, we stay in the default autocommit mode unless the application (module) says otherwise. Since the core uses MyISAM by default, there is no benefit to an explicit transaction, so we don't interfere. For application use, forcing a transaction would break things, since in MySQL transactions cannot nest. It also gets complicated if you are using DDL in the application.
The autocommit behavior already accomplishes what you suggest adding, and the application can easily change that by issuing its own START TRANSACTION.
Lots of the details change in 2.6, and explicit transactions are already used there.
For the database transactions, we stay in the default autocommit mode unless the application (module) says otherwise. Since the core uses MyISAM by default, there is no benefit to an explicit transaction, so we don't interfere. For application use, forcing a transaction would break things, since in MySQL transactions cannot nest. It also gets complicated if you are using DDL in the application.
The autocommit behavior already accomplishes what you suggest adding, and the application can easily change that by issuing its own START TRANSACTION.
Lots of the details change in 2.6, and explicit transactions are already used there.
154
Good catch @goffy!
Seems like we should have a "new user created" event triggered when a user is added. That way, profile could listen for that and add its extras as needed. I'll give that some thought.
Thanks!
Seems like we should have a "new user created" event triggered when a user is added. That way, profile could listen for that and add its extras as needed. I'll give that some thought.
Thanks!
155
The mysqli extension is required as of 2.5.8.
From what I read it is usually installed and enabled in fresh XAMPP installs, but make sure your php.ini has this line:
From what I read it is usually installed and enabled in fresh XAMPP installs, but make sure your php.ini has this line:
extension = php_mysqli.dll
156
Just to clarify one important point, this statement has been in every 2.5.8 announcement since RC1.
Quote:
For many years, XOOPS has been suppressing messages like the following:
We removed the code that suppressed these as part our drive to improve code quality in XOOPS.
Those "errors" have been happening silently since the transition from PHP 4 to PHP 5. The code still works, just like it did before we started showing the message. Making the message available in the logger is essential to helping the developers in making sure they get fixed.
I also want to take this opportunity to say a sincere thank you to Mamba for all the work I know he has already invested in cleaning up hundreds of these and similar issues already!
Quote:
... In previous XOOPS versions, E_STRICT warnings have been suppressed when using the debugging logger. These are no longer suppressed to give developers insight into what may need to be fixed. We've tried to make sure XoopsCore runs clean, but modules may produce debugging output you have not seen with earlier versions.
For many years, XOOPS has been suppressing messages like the following:
Only variables should be assigned by reference in file ...
We removed the code that suppressed these as part our drive to improve code quality in XOOPS.
Those "errors" have been happening silently since the transition from PHP 4 to PHP 5. The code still works, just like it did before we started showing the message. Making the message available in the logger is essential to helping the developers in making sure they get fixed.
I also want to take this opportunity to say a sincere thank you to Mamba for all the work I know he has already invested in cleaning up hundreds of these and similar issues already!
157
In XOOPS 2.5.8, the obsolete mysql extension is replaced with mysqli. The two extensions have lots of similarities, but a number of little differences. It looks like this version is depending on the mysqli connection in the new 2.5.8.
This should work:
but ... there may be other problems elsewhere.
Calls that go through the XoopsMySQLDatabase, including everything going through the standard XoopsObject handlers, will work fine without change. But anything that directly uses the mysql_* calls breaks. Since the mysql extension does not exist in the most recent PHP, anything depending on it needs to be changed to continue working.
This should work:
$mysql_version = substr(trim(mysql_get_server_info()), 0, 3);
but ... there may be other problems elsewhere.
Calls that go through the XoopsMySQLDatabase, including everything going through the standard XoopsObject handlers, will work fine without change. But anything that directly uses the mysql_* calls breaks. Since the mysql extension does not exist in the most recent PHP, anything depending on it needs to be changed to continue working.
158
In the insert cycle it will actually construct more than one sql string with the name input, one to check the name availability, and one to insert. Both of those need to be escaped. The same kind of issues hit other columns and tables, too, i.e. breeder names.
I've fixed those issues and more on the current development version on github:
https://github.com/XoopsModules25x/pedigree
All new efforts will be focused on this repository. Reports against this repository are more likely to get acted on. We don't have the bandwidth to support multiple versions, and this one already has a large number of changes which are essential to working in newer environments, as well as numerous security fixes.
Once this foundation work is complete, we can begin to address some of the UI issues that have been discussed.
I've fixed those issues and more on the current development version on github:
https://github.com/XoopsModules25x/pedigree
All new efforts will be focused on this repository. Reports against this repository are more likely to get acted on. We don't have the bandwidth to support multiple versions, and this one already has a large number of changes which are essential to working in newer environments, as well as numerous security fixes.
Once this foundation work is complete, we can begin to address some of the UI issues that have been discussed.
159
Thanks for the report, it was very helpful.
There are new updates on GitHub. It includes fixes for the error you found that was causing the blank screens. It also corrrects a few issues in some update functions, plus the issues causing the strict warning messages were corrected. Any feedback would be appreciated.
Pedigree looks like a very interesting module. The unique domain logic of the coefficient of inbreeding calculations, and the various pedigree charts look quite useful. It does have a very dated look, but updating the UI would be a very worthwhile effort since the underlying logic is so specific. I'm not sure I will have the time to devote to that right now, but I do have a client that might be interested -- that can change the priorities quickly.
Thanks again.
There are new updates on GitHub. It includes fixes for the error you found that was causing the blank screens. It also corrrects a few issues in some update functions, plus the issues causing the strict warning messages were corrected. Any feedback would be appreciated.
Pedigree looks like a very interesting module. The unique domain logic of the coefficient of inbreeding calculations, and the various pedigree charts look quite useful. It does have a very dated look, but updating the UI would be a very worthwhile effort since the underlying logic is so specific. I'm not sure I will have the time to devote to that right now, but I do have a client that might be interested -- that can change the priorities quickly.
Thanks again.
160
The Pedigree module on GitHub has been updated with the changes mentioned before, plus it no longer uses the mysql extension calls that caused it to fail under PHP 7. It does still toss some warning messages, but it does seem to work.
It is now at Alpha 6, and testing by anyone familiar with Pedigree would be greatly appreciated.
It is now at Alpha 6, and testing by anyone familiar with Pedigree would be greatly appreciated.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|