Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.3.0, Aquidneck
-
Fix Version/s: 1.5.0, 2.0.0, sprint 13: 11-28-2012, Aquidneck
-
Component/s: Content Editor
-
Labels:None
-
Sprint:Sprint 12, Sprint 13
Description
An Optus brand campaign (SEA:1309, Acct: 437) didn't deploy successfully because a keyword with a special character was rejected by Google. It appears from the DB that the keyword is stored in the content_model DB properly, but it gets corrupted in the content_editor_google DB.
mysql> select ke.*, campaignID, adGroupID, g.status, k.id, k.searchEngineIdentifier 'kident', text, keywordType, isNegative, k.status from gce_campaign c join gce_adGroup g on campaignID=c.id join gce_keyword k on adGroupID=g.id join gce_keywordError ke on ke.keywordID = k.ID where c.ID=1309;
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| keywordID | errorCode | errorText | reason | policyName | field | trigger | isExemptable | campaignID | adGroupID | status | id | kident | text | keywordType | isNegative | status |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 77193 | 0 | CriterionError | CriterionError.KEYWORD_HAS_INVALID_CHARS | operations[29].operand.criterion.text | false | 1309 | 1309 | Enabled | 77193 | NULL | the living room caf? port macquarie | Phrase | false | Active |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
