help to better help you:
Please: add always Joomla / JEM version and details to your posts, so we can try to reproduce your issue!
[SOLVED] Problem with Contacts
[SOLVED] Problem with Contacts
8 years 3 weeks ago
I have been using JEM 2.1.6 (now updated to 2.2.0) on Joomla 3.6.4 and it appears to work well. However, I have a problem when adding the contact to an event. The selection mechanism works well, BUT when adding a more recent contact, it saves as an incorrect entry. I have had to turn off the display of the contact on the Event page.
As a clue to what is happening, I investigated the Contacts info and found that the ID of the entry that displays wrongly is 127...
I know little about programming, but the number seems signifigant. Does the index size for the contacts in JEM need to be bigger ? and if so, can it be easily fixed ?
As a clue to what is happening, I investigated the Contacts info and found that the ID of the entry that displays wrongly is 127...
I know little about programming, but the number seems signifigant. Does the index size for the contacts in JEM need to be bigger ? and if so, can it be easily fixed ?
Please Log in or Create an account to join the conversation.
Re: [SOLVED] Problem with Contacts
8 years 3 weeks ago - 8 years 3 weeks ago
Thanks,
Yes, I can reproduce this. This would be good to be fixed.
I put this to github
EDIT:
I tested: it seems contact IDs > 127 aren't accepted
I tested 123 ok
I tested 125 ok
I tested 128 not ok
I tested 129 not ok
Yes, I can reproduce this. This would be good to be fixed.
I put this to github
EDIT:
I tested: it seems contact IDs > 127 aren't accepted
I tested 123 ok
I tested 125 ok
I tested 128 not ok
I tested 129 not ok
Last edit: 8 years 3 weeks ago by jojo12.
Please Log in or Create an account to join the conversation.
Re: [SOLVED] Problem with Contacts
8 years 3 weeks ago
Hi mickspice,
thanks for your report. It's really a bug. :whistle:
The contactid field of events table is defined as tinyint which allows values up to 127.
You can immediately fix this by altering the tyble structure. You can
(a) manually change type of contactid field from tinyint(4) to int(10) (the numbers are not important, sometimes you'll see (10), sometimes (11))
(b) execute the sql statement
where "(prefix)" is the specific prefix of your tables.
After this you have to check all contact ids of 127 and correct them as needed.
btw: The next JEM version will also execute the sql statement shown above. But already having the field as int is no problem, update will work fine.
thanks for your report. It's really a bug. :whistle:
The contactid field of events table is defined as tinyint which allows values up to 127.
You can immediately fix this by altering the tyble structure. You can
(a) manually change type of contactid field from tinyint(4) to int(10) (the numbers are not important, sometimes you'll see (10), sometimes (11))
(b) execute the sql statement
Code:
ALTER TABLE `(prefix)_jem_events` CHANGE `contactid` `contactid` int(10) NOT NULL DEFAULT '0';
After this you have to check all contact ids of 127 and correct them as needed.
btw: The next JEM version will also execute the sql statement shown above. But already having the field as int is no problem, update will work fine.
Please Log in or Create an account to join the conversation.
Re: [SOLVED] Problem with Contacts
8 years 3 weeks ago
Many thanks for the quick fix. I hadn't expected such great service.
As I have never used MySQL I am reluctant to do the changes manually, and will happily wait for the next update.
As I have never used MySQL I am reluctant to do the changes manually, and will happily wait for the next update.
Please Log in or Create an account to join the conversation.
Time to create page: 0.538 seconds