-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Full URL paths to templates should be relative to make it easier to deal with domain changes #410
Comments
Closing following 2.6 release. Please reopen if still an issue |
Thanks for the update. I don't see it listed in the release notes but I assume it's there. By the way, how do we trigger the urls getting fixed? Do we have to manually run the API? I see |
@herbdool I've reopened as it sounds like it's still an issue - we had 76 issues open which is pretty unmanageable :-) |
I believe the change to relative url's would also fix the CORS issue for people using Multisite? The only other alternative I see is enabling CORS for the discrete list of domains on the multisite. Not as good as as a solution and maybe that is not even advisable.
|
I went down a rabbit hole trying to figure out why Mosaico was showing CORS errors after the client updated their default domain (using the raw domain instead of www.). Turns out just clearing CiviCRM cache and rebuilding Smarty templates isn't enough.
In the table
civicrm_mosaico_template
themetadata
stores the full URL to the template. As far as I can tell there's no way to change that from the UI. Surely there's a better way to store the URLs so that sites can be moved to new domains or development/staging sites can be set up.The text was updated successfully, but these errors were encountered: