Nubuilder 4.5

[miasoft]

i have updated version to 4.5.
There are a lot of useful features. Great job! Tnx!

[kev1n]

Thanks miasoft !

[apmuthu]

@kev1n: Good Job.

Two non nudb files use the Null coalescing (??) operator not available in pre PHP 7 in nubuilder 4.5.
The minimum requirements are stated to be PHP 5.4.

Those using XAMPP v1.8.2.5 will have PHP 5.4.27.

These 2 files can be edited to work:

Change core/nucommon.php at line 249:

Code: Select all

return $o[$k] ?? $d;

replacing it with:

Code: Select all

return isset($o[$k]) ? $o[$k] : $d;

Change nuform.php at line 1125:

Code: Select all

$formAndSessionData->filter 		= $_POST['nuFilter'] ?? null;

replacing it with:

Code: Select all

$formAndSessionData->filter 		= isset($_POST['nuFilter']) ? $_POST['nuFilter'] : null;

Wonder what replacing absence with null serves.

Replace the core/libs/nudb v5.0.4 with phpMyAdmin 4.0.10.17 and add in the attached config.inc.php in core/libs/nudb/ folder.

phpMyAdmin version is in the core/libs/nudb/ChangeLog file.

Please note that the default database name in nuconfig.php is still nubuilder4 with DBuser as nuadmin and DBPassword set as some text.

[kev1n]

@kev1n: Good Job.

Two non nudb files use the Null coalescing (??) operator not available in pre PHP 7 in nubuilder 4.5.
The minimum requirements are stated to be PHP 5.4.

Thanks, I replaced the Null coalescing operator.

[apmuthu]

@kev1n: Thanks. Your commit does it.

Also use 1 INSERTstatement for each language in nubuilder4.sql.

Please re-release the v4.5.

[kev1n]

Also use 1 INSERTstatement for each language in nubuilder4.sql.

nubuilder4.sql is generated automatically. I don't have much control over its creation.
What would be the advantage of having separate insert statements? If you don't want to have all languages in your db, run some post-installation scripts to remove them

[apmuthu]

What is the process by which the nubuilder4.sql gets automatically created?
Having 1 insert per language can then allow for placing all language inserts in a separate lang folder and then selectively create the enduser nubuilder4.sql file with just the languages needed without any post install scripts. Mapping and managing translations would be easy for new language file creators.

[apmuthu]

Attached are the changed files in dev v4.5 as of commit #267 replacing every leading 4 spaces with tab character

[apmuthu]

Duplicate German 3 Translations can be removed with:

Code: Select all

DELETE FROM zzzzsys_translate WHERE zzzzsys_translate_id IN (
'nu5ec114f2585bf45',
'nu5ec114f2586fae8',
'nu5fe60f1c6b83a52'
);

Choosing to retain the later ones, committed by @kev1n as #268.

Identify duplicate strings with:

Code: Select all

SELECT trl_language, trl_english, COUNT(*) AS records FROM `zzzzsys_translate` 
GROUP BY trl_language, trl_english HAVING records > 1;

[apmuthu]

There is a Russian language string translation required for the English string "Font Weight". The current v4.5 sql has the following:
Насыщенность шрифта
Размер шрифта

Many translation engines come up with:
Вес шрифта

Any native Russians, please contribute the preferred translation.