You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 8, 2022. It is now read-only.
I think this behavior changed in SEO Pro 1.2.2 pl: Add count back to pagetitle & longtitle.
This becomes problematic when updating SEO Pro on an existing site that contains resources with page- and longtitles beyond the limit. Users can't save these resources anymore now all of a sudden.
I would personally prefer to control this with a system setting. Strictly enforce character count: yes/no. There are other scenarios where you'd want to allow longer titles, for example when you import content or take over an old site for optimization.
The text was updated successfully, but these errors were encountered:
This workaround isn't working with ModX Revo 2.7.1 - seoPro 1.3.0 and Articles 1.7.11. Editing already stored blog records results in a warning for Article Title fields exceeding the number of allowed characters.
We really need to be able to specify whether SEOPro will prevent saving if fields are over the character count. I have a client who wants to use this as a guide, but not something that prevents saving resources. For now, I've disabled the line in the code that alters the maximum allowed field length.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think this behavior changed in SEO Pro 1.2.2 pl: Add count back to pagetitle & longtitle.
This becomes problematic when updating SEO Pro on an existing site that contains resources with page- and longtitles beyond the limit. Users can't save these resources anymore now all of a sudden.
I would personally prefer to control this with a system setting. Strictly enforce character count: yes/no. There are other scenarios where you'd want to allow longer titles, for example when you import content or take over an old site for optimization.
The text was updated successfully, but these errors were encountered: