- Forum||Hilfe & Support
- /
- KISS Support Forum
- /
- Software Forum
- /
- KISS Advertiser
- /
- v.1.5.61 postcode field length changed
v.1.5.61 postcode field length changed
Fantastic - extending the VARCHAR on ad_post solved my problem and now google map is accurate. Thanks
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
- DocChicago
- Offline
- KISS Programmer-in-Chief
The postcode is stored in the customer\'s table (encrypted) and is taken over from that table upon creating an ad by the customer. It is then stored with the ad in the <prefix>_ksads_ads table, field ad_post.
This is necessary because the customer\'s postcode can be different from the ad\'s postcode, i.e. if the article in the ad has another location which often applies to real estates.
Please try to adjust the postcode in the ad\'s table. The field has a length of 10 characters which should be sufficient as the postcode in the ads table is not encrypted.
The \'item location\' always displays the combination of postcode and city.
Example
In German 59227 Ahlen (postcode first)
in all other languages Ahlen, 59227 (postcode last)
Ob ein Glas halb voll oder halb leer ist, ist mir egal. Hauptsache meine Zähne passen rein.
No matter whether a glass is half full or half empty - as long as my teeth fit in.
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
thanks for the quick response.
I have changed ksads_customers cust_postcode to varchar (20) successfully.
and now manage to save the full length of postcode in customer data. However, in the actual Ad it appears to concatenate postcode and location calling it Item Location. This does not use the full length of the postcode. is there another field in an other table?
any ideas?
thanks
Haydn
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
- DocChicago
- Offline
- KISS Programmer-in-Chief
Oh, you are talking about the customer\'s postcode - I thought you meant the ad address postcode.
The truncation of the postcode is probably caused by the fact that customer data are stored to the database in an encrypted way. As the encrypted data are longer than the clear data, they might be truncated if the total length of the encrypted data exceeds 10 characters.
To avoid this, set the length of the \'cust_postcode\' field in the database table \'<prefix>_ksads_customers\' to 20. (it is 10 now). From the next version on we will install it with a length of 20. We think 20 is long enough to store the 8-digit postcodes with spaces correctly, even if they are encrypted.
Ob ein Glas halb voll oder halb leer ist, ist mir egal. Hauptsache meine Zähne passen rein.
No matter whether a glass is half full or half empty - as long as my teeth fit in.
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
Dear Support
First - apologies if I am doing somthing really stupid..
I will try by images to show you what I mean s happening..
I noticed that the Customer DATA is loosing last 2 character on postcode as per:
Then I logged in as customer and added the missing two characters as per
the saved
then went back to ad - postcaoise characters missing again
check Database as stated 10 character allowed
Could it be to do with Community Builder? can you tell me what is going wrong?
thanks in anticpation
Haydn
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
- DocChicago
- Offline
- KISS Programmer-in-Chief
The database field is ad_post in the table ksads_ads.
But the field allows already 10 characters. In KISS Advertiser, the postcode is not truncated, if you enter 10 characters, they are stored to the database. The postcode is submitted to the Google maps plugin with its full length.
Ob ein Glas halb voll oder halb leer ist, ist mir egal. Hauptsache meine Zähne passen rein.
No matter whether a glass is half full or half empty - as long as my teeth fit in.
Bitte Anmelden oder Registrieren um der Konversation beizutreten.