1913
I was trying to update the navbar and was under the assumtion that themes/xbootstrap/tpl/nav-menu.tpl was the correct file when using them xboostrap.
When I refresh my browser my changes are not coming up, restarting my webserver won't work either.
cleaning the data/caches/ folder won't work either
In an attempt to disable caching I have attempted
$tpl->caching = 0; in backend.php file with no success either.
Anyone know how I can work on the template and have my changes reflected straight after browser refresh ? If caching is the issue here how to disable it?
When I refresh my browser my changes are not coming up, restarting my webserver won't work either.
cleaning the data/caches/ folder won't work either
In an attempt to disable caching I have attempted
$tpl->caching = 0; in backend.php file with no success either.
Anyone know how I can work on the template and have my changes reflected straight after browser refresh ? If caching is the issue here how to disable it?
1915
Thanks Mamba for your help got it sorted now.
I can update mysql on my server but my hosting provider won't so need to stick to the version I have.
I can update mysql on my server but my hosting provider won't so need to stick to the version I have.
1916
No, try changing the line 51 to:
The issue is with the MySQL key length limitations: it's 767 bytes is the stated prefix limitation for InnoDB tables in MySQL version 5.6 (and prior versions). It's 1,000 bytes long for MyISAM tables.
In MySQL version 5.7 and upwards this limit has been increased to 3072 bytes.
The indexes worked fine with utf8_unicode_ci, since it uses 3 bytes per character, but when you're using utf8mb4_unicode_ci, you're adding extra byte, as it is using 4 bytes, and you're going over the limit.
MySQL 5.7 avoids the problem. Consider upgrading
KEY `sort` (`step_order`, `step_name`(240)) The issue is with the MySQL key length limitations: it's 767 bytes is the stated prefix limitation for InnoDB tables in MySQL version 5.6 (and prior versions). It's 1,000 bytes long for MyISAM tables.
In MySQL version 5.7 and upwards this limit has been increased to 3072 bytes.
The indexes worked fine with utf8_unicode_ci, since it uses 3 bytes per character, but when you're using utf8mb4_unicode_ci, you're adding extra byte, as it is using 4 bytes, and you're going over the limit.
MySQL 5.7 avoids the problem. Consider upgrading
1917
Doing the change as requested moved the problem to table "profile_regstep" (line 43 in same file you mentioned)
So I have then changed to (line 45) and it installed the module fine.
Do you have an idea on what is going on?
So I have then changed
`step_name` varchar(255) `step_name` varchar(200) Do you have an idea on what is going on?
1918
The utf8mb4_unicode_ci is supported, but it looks like it needs more space for the Unique Key than the database has.
So in the Profile's MySQL file (/sql/mysql.sql) change line 30 to something like:
and try again.
If the problem is still there, go lower with the number, let's say:
175, 150, 125, 100
That should fix the issue.
So in the Profile's MySQL file (/sql/mysql.sql) change line 30 to something like:
UNIQUE KEY `field_name` (`field_name`(200)), and try again.
If the problem is still there, go lower with the number, let's say:
175, 150, 125, 100
That should fix the issue.
1919
Setup of the server:
XOOPS Version XOOPS 2.5.10
PHP Version 7.2.22
mySQL Version 5.7.27-0ubuntu0.16.04.1 - (Ubuntu)
OS Linux Ubuntu Server
Creating database at install won't work with my current provider so I need to create database beforehand. The default charset for my provider is utf8mb4_unicode_ci.
When using this, I can't install the user profile module and it is showing the following MySQL related error.
If I force the database into utf8_general_ci the installation would work fine.
I have read somewhere that since MySQL 5.5.3 is advised.
Is there no support yet for XOOPS runing on utf8mb4_unicode_ci?
I have little understanding of the issue nor the effect of changing character set on database but I ham fully admin on my server so can run any commands for debug if required.
My aim is to reproduce an environment as close as possible to our hosting service for future website migration.
XOOPS Version XOOPS 2.5.10
PHP Version 7.2.22
mySQL Version 5.7.27-0ubuntu0.16.04.1 - (Ubuntu)
OS Linux Ubuntu Server
Creating database at install won't work with my current provider so I need to create database beforehand. The default charset for my provider is utf8mb4_unicode_ci.
When using this, I can't install the user profile module and it is showing the following MySQL related error.
0.000255 - CREATE TABLE profile_field ( `field_id` int(12) unsigned NOT NULL auto_increment, `cat_id` smallint(5) unsigned NOT NULL default '0', `field_type` varchar(30) NOT NULL default '', `field_valuetype` tinyint(2) unsigned NOT NULL default '0', `field_name` varchar(255) NOT NULL default '', `field_title` varchar(255) NOT NULL default '', `field_description` text, `field_required` tinyint(1) unsigned NOT NULL default '0', `field_maxlength` smallint(6) unsigned NOT NULL default '0', `field_weight` smallint(6) unsigned NOT NULL default '0', `field_default` text, `field_notnull` tinyint(1) unsigned NOT NULL default '0', `field_edit` tinyint(1) unsigned NOT NULL default '0', `field_show` tinyint(1) unsigned NOT NULL default '0', `field_config` tinyint(1) unsigned NOT NULL default '0', `field_options` text, `step_id` smallint(3) unsigned NOT NULL default '0', PRIMARY KEY (`field_id`), UNIQUE KEY `field_name` (`field_name`), KEY `step` (`step_id`, `field_weight`) ) ENGINE=MyISAM
Error number: 1071
Error message: Specified key was too long; max key length is 1000 bytes If I force the database into utf8_general_ci the installation would work fine.
I have read somewhere that since MySQL 5.5.3 is advised.
Is there no support yet for XOOPS runing on utf8mb4_unicode_ci?
I have little understanding of the issue nor the effect of changing character set on database but I ham fully admin on my server so can run any commands for debug if required.
My aim is to reproduce an environment as close as possible to our hosting service for future website migration.
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 |
 |
|