tagMe

Hello,

Thanks for getting in touch. Can you share a screenshot and explain what changes are you looking for. That would help us to better understand the requirement.

Thanks & Regards, Team Urdhva Tech.

I have also located the following errors in my Apache log files when attempting to change the values of existing tags:

[Fri Jul 27 17:23:33.773453 2018] [proxy_fcgi:error] [pid 15595:tid 140255789090560] [client 115.69.171.154:65193] AH01071: Got error 'PHP message: PHP Warning:  Declaration of SugarFieldUtagme::getSearchWhereValue($value, $seed, $field_name, $customField) should be compatible with SugarFieldBase::getSearchWhereValue($value) in /mysuitecrminstall/custom/include/SugarFields/Fields/Utagme/SugarFieldUtagme.php on line 0\nPHP message: PHP Warning:  Declaration of SugarFieldUtagme::save($bean, $inputData, $field, $def, $prefix = '') should be compatible with SugarFieldBase::save(&$bean, $params, $field, $properties, $prefix = '') in /mysuitecrminstall/custom/include/SugarFields/Fields/Utagme/SugarFieldUtagme.php on line 0\n', referer: https://crm.ibo.edu.au/index.php

[Fri Jul 27 17:24:22.784390 2018] [proxy_fcgi:error] [pid 11118:tid 140256225511168] [client 115.69.171.154:65219] AH01071: Got error 'PHP message: PHP Warning:  Declaration of SugarFieldUtagme::getSearchWhereValue($value, $seed, $field_name, $customField) should be compatible with SugarFieldBase::getSearchWhereValue($value) in /mysuitecrminstall/custom/include/SugarFields/Fields/Utagme/SugarFieldUtagme.php on line 0\nPHP message: PHP Warning:  Declaration of SugarFieldUtagme::save($bean, $inputData, $field, $def, $prefix = '') should be compatible with SugarFieldBase::save(&$bean, $params, $field, $properties, $prefix = '') in /mysuitecrminstall/custom/include/SugarFields/Fields/Utagme/SugarFieldUtagme.php on line 0\n', referer: https://crm.ibo.edu.au/index.php?action=DetailView&module=Contacts&record=2ed04352-223d-5be6-b07c-5b598d54bbc0&offset=1

Hello,

Thanks for drawing an attention towards multiple TagMe MassUpdate fields. We will take into consideration and will include in the future release version. We will let you know once released the version with the functionality. Also, we will look into the Apache log.

Thanks & Regards, Team Urdhva Tech.

Have just attempted to import records into my SuiteCRM Leads module. Part of the import had content to be imported to a tagMe field - the import errored out with the following return:

WARNING: [2] Declaration of SugarFieldUtagme::getSearchWhereValue($value, $seed, $field_name, $customField) should be compatible with SugarFieldBase::getSearchWhereValue($value) on line 0 in file /mysuitecrminstall//custom/include/SugarFields/Fields/Utagme/SugarFieldUtagme.php
WARNING: [2] Declaration of SugarFieldUtagme::save($bean, $inputData, $field, $def, $prefix = '') should be compatible with SugarFieldBase::save(&$bean, $params, $field, $properties, $prefix = '') on line 0 in file /mysuitecrminstall//custom/include/SugarFields/Fields/Utagme/SugarFieldUtagme.php

I removed the tagMe field from the import mapping and the import completed successfully - thanks for your time and patience

Have another issue with the tagMe function. When I create a new tag, some of the URL's generated to search/filter the records are incorrect, please see the attached image

As you can see there are two fields in the image, Permissions and Business Type. The Business Type field has a tag with content Medium. If I click on the Tag it generates the URL that you can see at the bottom of the image, that URL references the permissions_c tagMe field NOT the business_type_c field that it should... Could you tell me what your latest version of the tagMe field module is please? Should I try a new install? Thanks for your time and patience

Hello,

We will check with multiple TagMe fields into a single module. Regarding the import warning message, it seems error reporting is on your server. Once you will off that setting that messages will not be displayed while importing. We will also check for the search URL once the module has multiple TagMe fields. Right Now, the latest version for the TagMe is 3.2.7 which is uploaded on the Store.

Thanks & Regards, Team Urdhva Tech.

Hello,

Can you please try after removing the browser cache? It will work properly then.

Thanks & Regards, Team Urdhva Tech.

Hey, I'm about to try installing your latest module to see if it clears up any of the problems we are having. Will I need to uninstall the existing installation and, if yes, should I remove the database tables when I uninstall it?

Thanks for your time and patience

Hey, installed the updated module, no change. I have edited a tagMe field in the contacts_cstm table, changing it from MEDIUM to SMALL. Save the database changes and viewed the record in Suite. Opened the record in Edit view, saved it WITHOUT making ANY changes and the field has reverted to MEDIUM!!! Do you have ANY thoughts on why/how this could be happening before I uninstall the module as unusable? Could it be permissions based?

Thanks for your time and patience

Sorry, forgot to say, when I made the changes in the database those changes were reflected in Suites Detail/Edit views, the value had changed from MEDIUM to SMALL

Hello,

Are you changing the value into TagMe field from Medium to Small or are you changing the TagMe field name? If you are changing the TagMe field name into the contacts_cstm table then it will not help because it needs other changes into field definition and fields_meta_data too.

As of now, TagMe supports only one TagMe type field into a single module.

It would be good come up on Skype, so we can address it fast. Our Skype id is: urdhvatech

Thanks & Regards, Team Urdhva Tech.

Hello,

We will check and consider your suggestion. If those are possible then we will include in the future version.

Thanks & Regards, Team Urdhva Tech.