-
Notifications
You must be signed in to change notification settings - Fork 18
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
Support for WordPress? #39
Comments
Sounds great! Should I maybe create a WP branch, so we can start collecting individual changes and merge everything in one go when we're done? |
Glad you're keen. I think we can create PRs without the need for a branch. We're scheduling this work for April. |
Could you give me a short info about the current state of CiviProxy for Wordpress? Is it supported at all? If one has a Wordpress Frontend, would it then go for a wordpress CiviCRM backend or a drupal CiviCRM as backend? |
I can confirm that CiviProxy with CiviCRM in wordpress works as expected. There was one issue with mosaico images in mailings. Fixed in PR #53 We also had to use the right tool for the civicrm cron. We first used |
Another issue we had on wordpress was the social media icons in the versafix template, see as well #38 |
Issue #39: added mosacio compatibility for wordpress
We'd like to add support for WordPress, and want to check if there are any concerns or guidance you'd like to provide.
I imagine we'd start with abstracting the URLs in https://github.com/systopia/CiviProxy/blob/master/proxy/config.dist.php so that we could specify in one place whether the CiviCRM instance is installed with Drupal or WordPress, then see what else is necessary.
The text was updated successfully, but these errors were encountered: