Blog Sections Open
Why tagLinks Can Fail on Latin Tags Even with UTF-8 Enabled
If Russian tags work and Latin tags fail, the issue is usually not raw encoding but how the tag parameter is normalized and matched in the request flow.
This donor described a confusing case: tagLinks worked for Cyrillic tags, but Latin tags returned “no records found” even though the database and CMS both used UTF-8.
Why this happens
Encoding may still be technically correct while the tag parameter is being normalized, transliterated, or matched differently in the request layer. That is why the problem can look like charset trouble even when the page URL looks clean.
What to check
- how the tag value is passed in the URL
- whether the comparison is case-sensitive
- how the tag data is stored in the TV or field
- whether another snippet in the chain rewrites the parameter
Recommendation
Debug the exact tag value before and after request parsing. If one script normalizes Cyrillic and Latin inputs differently, the filter can fail even though the visible URL looks fine.
Validating a Required TV Before Saving a Resource
If a TV must never be left empty, the save flow should stop before persistence and show the editor a clear message instead of silently accepting bad data.
Fixing phpthumb Paths That Duplicate the Image Directory
If phpThumb returns a doubled path, the problem is usually how the input path is passed into the snippet, not phpThumb itself.