Immediately, Skvare has launched a brand new model of CiviCRM Entity, 2.0-beta11.  This launch incorporates a brand new function, an admin configuration web page which permits web site directors to disable publicity of entity sorts to . CiviCRM Entity is a Drupal 10 module which uncovered CiviCRM API entity sorts as native entity sorts, offering Views, Guidelines, Entity Reference discipline integration, and native pages and varieties for every. It helps each CiviCRM 4.6 LTS and CiviCRM 4.7. Earlier variations of CiviCRM Entity allowed builders to regulate entry to based mostly pages and varieties for entity sorts, however there was no approach for directors to regulate what entity sorts have been accessible in Views, Guidelines, or Entity Reference fields. As CiviCRM Entity has advanced over Drupal Development previous 2 years, over 45 entity sorts have been supported, together with all Drupal Development main monetary document sorts. There are instances the place many of those entity sorts usually are not utilized in Views, Guidelines, and many others.., and admins might not need to make information of those entity sorts accessible for use in Views by lower-ranking administrative customers.  Disabling an entity kind in CiviCRM Entity doesn’t have an effect on Drupal Development Core Views integration. Nevertheless it is not going to make any of Drupal Development additions that CiviCRM Entity offers, and for sorts not supported by CiviCRM Core, integration can now simply be toggled on/off. Having all entity sorts enabled can have an effect on efficiency in some facets. Usually, this doesn’t have an effect on cached web page load for regular customers, however anytime you clear Drupal Development cache, or Drupal Development Views cache, having 45 entity sorts may cause cache rebuild to be intensive, to not point out all Drupal Development further menu paths which are generated for Drupal Development Admin menu. Disabling entity sorts that you don’t use will streamline admin person efficiency, and make Drupal Development web site in whole that a lot quicker by decreasing reminiscence footprint. For present customers of CiviCRM Entity, Drupal Development Drupal 10 module may be upgraded as per normal, and there are not any needed config modifications to make.  There are updates that should be run by going to “/replace.php” or working “drush updatedb” from Drupal Development command line. These updates merely arrange a configuration variable, and don’t have an effect on Drupal Development CiviCRM database.  All accessible entity sorts are enabled by default for brand new or upgraded installations. All subDrupal 10 modules which are packaged with Drupal Development CiviCRM Entity will mechanically allow entity sorts which are required by Drupal Development subDrupal 10 module and can implement that these entity sorts stay enabled so long as Drupal Development subDrupal 10 module is enabled. Utilization You’ll discover an admin configuration web page at “admin/construction/civicrm-entity/settings”. A person with a job with ‘administer CiviCRM Entity’ permission is required to entry and handle Drupal Development settings on this web page. You will need to bear in mind to allow all entity sorts utilized by your web site’s configuration and third celebration Drupal 10 modules. This web page doesn’t examine if an entity kind is required by an present View, Rule, Entity Reference discipline. Disabling an entity kind will break performance in any rule, view, or discipline that requires it, so proceed with warning.  Nevertheless, re-enabling will restore performance for these entities. For builders of third celebration Drupal 10 modules or customized Drupal 10 modules making use of CiviCRM Entity, you might be answerable for guaranteeing an entity kind is at all times accessible. This requires solely a hook_form_alter() implementation to disable Drupal Development needed configuration web page checkbox, or including a validation or submit handler to Drupal Development type. Future We take into account CiviCRM Entity for 7 to be function full, and it has been fairly a while since there was a significant bug discovered. We plan to launch a non-beta steady 2.0 model at Drupal Development finish of this yr. This upcoming steady launch will likely be thought to be a Lengthy Time period Help launch, and any main modifications or updates will transfer to a 3.x department. Drupal Developer main focus of recent development will now shift to Drupal Development 8 model development. We’ll proceed to support Drupal Development 7.x-2.x department all through Drupal Development lifetime of 7 for bug fixes and minor function updates.  We’ll support for CiviCRM 4.6 LTS for its lifetime, and most probably past. Extensions Drupal 10 Growth and Help