The first release of the Yootheme CiviCRM Bridge enabled users to display contacts on their WordPress or Joomla website, but did not allow users to drill down and view a single record.
With a bridge between Yootheme Pro and CiviCRM, publishing CiviCRM content on the front end of your Joomla! or WordPress website just got a lot easier!
There was recently changes to WordPress that is changing the way redirect_canonical works. You can view the details in our GitLab issue #49 , If you want further details you can see all of the WordPress issues related to how redirects are done. These changes are designed to better handle rel="canonical" in WP.
Introducing WordPress Content Views for CiviCRM which uses the new Data Processor extension for CiviCRM to provide easy to design and beautiful layouts and listings of CiviCRM information on your WordPress website.
Have you ever wondered, how can I give a group of contacts specific capabilities? We have too. And now you can! Introducing the CiviCRM Groups Sync Plugin (CGS). This plugin provides a new way for access control to be managed that associates a group of users in WordPress to a group of contacts in CiviCRM. Taking away the need to create a new WordPress user role anytime someone needs a slightly different kind of access to CiviCRM.
In the past few weeks we have been looking at how a more uniform user experience could be provided between CiviCRM and WordPress dashboards. We looked at potentially leveraging Shoreditch, but quickly realized that it's dependent on a Drupal theme and the readme clearly stated that is was only for Drupal. So we stepped back and looked at how we could do this with CSS changes that apply to the admin only, since this is not affected by the theme at all.
Tadpole has been working with Andrei Mondoc, the developer of CFC, to extend the availability of processors to support memberships. Since memberships typically use Price Sets, this work also allows for Donations that use Price Sets and Line Items within a contribution page.
The civicrm-setup library aims to replace the CiviCRM installer. Following the December/January iteration, it's available for use as a CLI installer and as a web-based WordPress installer.
The first time a WordPress version of CiviCRM was available it was version 4.1 back in February 2012. It has now been more than 5 years, and I thought it would be nice to outline what has happened since WordPress became available as a CMS option for CiviCRM.
When email was first designed, security was not considered important and up until fairly recently it was still possible to send an email from any address and get away with it.
