WordPress issueshttps://lab.civicrm.org/dev/wordpress/-/issues2023-12-06T17:13:05Zhttps://lab.civicrm.org/dev/wordpress/-/issues/111Civi Shortcode does not work when added in ACF fields2023-12-06T17:13:05ZKurund JalmiCivi Shortcode does not work when added in ACF fieldsSteps to replicate:
* Add ACF field of type 'textarea' for page
* Add CiviCRM shortcode in that field
* View the page, it displays blank instead of civicrm content
I have tested this on vanilla civicrm + acf plugin.
Any thoughts on th...Steps to replicate:
* Add ACF field of type 'textarea' for page
* Add CiviCRM shortcode in that field
* View the page, it displays blank instead of civicrm content
I have tested this on vanilla civicrm + acf plugin.
Any thoughts on the best way to resolve this?https://lab.civicrm.org/dev/wordpress/-/issues/106Add shortcode support for profile map view2021-07-29T18:09:38ZKurund JalmiAdd shortcode support for profile map viewCurrently, map view for profile is not supported using shortcode.
I can't remember if it was there initially and was removed or was never implemented hence, wanted to check here.
I can add this feature and submit PR if everyone agrees :)Currently, map view for profile is not supported using shortcode.
I can't remember if it was there initially and was removed or was never implemented hence, wanted to check here.
I can add this feature and submit PR if everyone agrees :)5.41.0https://lab.civicrm.org/dev/wordpress/-/issues/99Support User Account properly for profiles2023-12-06T21:29:55ZJoeMurraySupport User Account properly for profilesCurrently, only Drupal properly implements the Used For options for Profiles. This issue chips away at the backlog for WordPress by proposing to properly support User Account.
1. Change the [x] option for User Account for all profiles s...Currently, only Drupal properly implements the Used For options for Profiles. This issue chips away at the backlog for WordPress by proposing to properly support User Account.
1. Change the [x] option for User Account for all profiles so that it is a checkbox widget.
1. If User Account is unchecked, do not change current behaviour of CiviCRM
1. If User Account is checked, expose the profile on wp-admin/user-edit.php?user_id=nnn and wp-admin/profile.php?user_id=nnn in an appropriate manner consistent with other plugin fields that are exposed. When Update Profile is clicked, validate the profile as appropriate for this form. Once the form is validated, save the field values as appropriate.
1. Create unit tests.JoeMurrayJoeMurrayhttps://lab.civicrm.org/dev/wordpress/-/issues/92Feature Request, CiviCRM Mailing, Public Page (ie. the page you use to read t...2023-02-09T16:50:04Zjustinfreeman (Agileware)Feature Request, CiviCRM Mailing, Public Page (ie. the page you use to read the email on-line) entirely bypass WordPress pages and are therefore rendered without website title, meta tags which negatively impacts sharing on social networksCurrently the CiviCRM Mailing, Public Page (ie. the page you use to read the email on-line) entirely bypass WordPress pages and are therefore rendered without website title, meta tags which negatively impacts sharing on social networks. ...Currently the CiviCRM Mailing, Public Page (ie. the page you use to read the email on-line) entirely bypass WordPress pages and are therefore rendered without website title, meta tags which negatively impacts sharing on social networks. See for example, https://civicrm.org/civicrm/mailing/view?reset=1&id=1686
If you share this page on a social network, it is expected by end users that you would see:
1. Organisation logo or at least a feature image
2. Short summary
3. Title of the newsletter
What you in fact see is very different. See for example https://developers.facebook.com/tools/debug/ using https://civicrm.org/civicrm/mailing/view?reset=1&id=1686
![screencapture-developers-facebook-tools-debug-2021-02-25-08_59_54](/uploads/d47e952a224080e34ad7d2ff08d99b3f/screencapture-developers-facebook-tools-debug-2021-02-25-08_59_54.png)
This is increasingly becoming a problem as CiviCRM sites re-share newsletters that they have recently sent out to their social networks.
The feature request is to provide a **Setting** which defines the **WordPress Page to be used to display the CiviCRM Mailing, Public Page** (ie. the page you use to read the email on-line). This is the same concept of the CiviCRM base page. On the CiviCRM Mailing page, a new shortcode would be present which is then used to render the public mailing.
The advantage of using a shortcode is that it then gives the website builder the ability to control how the page is presented, what metatags are used on that page and the template to be used for that page.
This is similar to the recent work to improve CiviCRM shortcode handling. See https://github.com/civicrm/civicrm-wordpress/pull/239 and https://lab.civicrm.org/dev/wordpress/-/issues/90
Ping @haystack and @kcristiano
Agileware Ref: CIVICRM-1662https://lab.civicrm.org/dev/wordpress/-/issues/39Refactor WordPress Code2020-06-06T12:58:42ZGhost UserRefactor WordPress CodeThe entire project could benefit from more modern coding practices I’d recommend the WordPress maintainers consider checking out https://phptherightway.com/
Performance is still a major issue with CiviCRM and WordPress.The entire project could benefit from more modern coding practices I’d recommend the WordPress maintainers consider checking out https://phptherightway.com/
Performance is still a major issue with CiviCRM and WordPress.https://lab.civicrm.org/dev/wordpress/-/issues/18wp-cli sometimes fails to find cms path2020-06-17T09:07:23Zaydunsaidan.saunders@squiffle.ukwp-cli sometimes fails to find cms pathInitially reported as https://github.com/veda-consulting/uk.co.vedaconsulting.mosaico/issues/293 but on further investigation the url issue only occurs when mailings are invoked by wp-cli.
When `wp-cli` is called with the `--path` optio...Initially reported as https://github.com/veda-consulting/uk.co.vedaconsulting.mosaico/issues/293 but on further investigation the url issue only occurs when mailings are invoked by wp-cli.
When `wp-cli` is called with the `--path` option but the current working directory is not within the CMS tree, `CRM_Utils_System_WordPress::cmsRootPath()` is unable to determine the CMS path resulting in the `realpath($cmsPath)` call in `CRM_Utils_System_WordPress::getCiviSourceStorage()` returning the current working directory and hence a bad value for the `$config->userFrameworkBaseURL` which is used when replacing trackable URL's in `CRM_Mailing_BAO_TrackableURL::getTrackerURL()`
A workaround is to hardcode in `civicrm.settings.php`:
`$civicrm_setting['URL Preferences']['userFrameworkResourceURL'] = 'https://domain.tld/wp-content/plugins/civicrm/civicrm';`
The fix is to save the `--path` setting so that `CRM_Utils_System_WordPress::cmsRootPath()` returns the right information.aydunsaidan.saunders@squiffle.ukaydunsaidan.saunders@squiffle.ukhttps://lab.civicrm.org/dev/wordpress/-/issues/13Clean URLs2020-06-17T09:07:22ZhaystackClean URLsOverview
----------------------------------------
Rather than raise a (perhaps) premature PR on GitHub, here's a follow-up to [PR-123](https://github.com/civicrm/civicrm-wordpress/pull/123) for WordPress people to test:
https://github.c...Overview
----------------------------------------
Rather than raise a (perhaps) premature PR on GitHub, here's a follow-up to [PR-123](https://github.com/civicrm/civicrm-wordpress/pull/123) for WordPress people to test:
https://github.com/christianwach/civicrm-wordpress/tree/cleaner-urls
Here's the original [Jira ticket](https://issues.civicrm.org/jira/browse/CRM-21788). There aren't any dependencies this time, though it requires a build from CiviCRM master to work correctly - or at minimum the code from these PRs:
* https://github.com/civicrm/civicrm-core/pull/13043
* https://github.com/civicrm/civicrm-core/pull/12969
* https://github.com/civicrm/civicrm-core/pull/12968
Plus enabling Clean URLs in "civicrm.settings.php":
```php
// check for WordPress clean URLs
elseif( function_exists('get_option') && get_option('permalink_structure') != '' ) {
define('CIVICRM_CLEANURL', 1);
}
```
I'd like to see the latest code which changes the CiviCRM-WordPress plugin's init sequence out in the wild before I raise a PR, but that allows some time to test this, which will inevitably be complicated.
Before
----------------------------------------
Basepage URLs are of the form:
```
https://domain.tld/civicrm/?page=CiviCRM&q=civicrm%2Fevent%2Finfo&reset=1&id=7
```
After
----------------------------------------
Basepage URLs are of the form:
```
https://domain.tld/civicrm/event/info/?reset=1&id=7
```haystackhaystackhttps://lab.civicrm.org/dev/wordpress/-/issues/11Code style2020-06-17T09:07:22ZhaystackCode styleI'd like to open a discussion about the code style used for the CiviCRM WordPress plugin. At present, the plugin (loosely) conforms to Drupal/CiviCRM code style conventions. Is this what we want?
Pros:
CiviCRM devs are used to space-in...I'd like to open a discussion about the code style used for the CiviCRM WordPress plugin. At present, the plugin (loosely) conforms to Drupal/CiviCRM code style conventions. Is this what we want?
Pros:
CiviCRM devs are used to space-indentation and compact code style
Cons:
WordPress devs may be put off from contributing by the current code style
My personal opinion:
I work almost exclusively with CiviCRM in WordPress. I'm comfortable with CiviCRM code style conventions for Core, but I would prefer if the WordPress plugin conformed to WordPress code style. Because it's a WordPress plugin.
https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/
Thoughts anyone?kcristianokcristianohttps://lab.civicrm.org/dev/wordpress/-/issues/36REST API calls using json param do not work in Wordpress context --backslashe...2020-06-06T12:56:59ZeileenREST API calls using json param do not work in Wordpress context --backslashes are addedThere is a long discussion on this on this PR but the approach still appears to be unresolved. I have closed the PR to track through gitlab
https://github.com/civicrm/civicrm-core/pull/12813
---
The issue:
When CiviCRM receives an API...There is a long discussion on this on this PR but the approach still appears to be unresolved. I have closed the PR to track through gitlab
https://github.com/civicrm/civicrm-core/pull/12813
---
The issue:
When CiviCRM receives an API request through `extern/rest.php` with a `json` parameter, and the CMS is WordPress, an error will result.
This is because Civi bootstraps WordPress to authenticate the API user, and WordPress escapes all quotation marks in `$_POST` variables whether or not PHP's `magic_quotes_gpc` is enabled. CiviCRM is not expecting an escaped string, and JSON decoding fails due to the extra backslashes. See `wp_magic_quotes()` which is called by `wp-settings.php` during bootstrap.https://lab.civicrm.org/dev/wordpress/-/issues/9Use WP Cron for CiviCRM Jobs on WP2020-06-17T09:07:22ZGhost UserUse WP Cron for CiviCRM Jobs on WPUse WP Cron for CiviCRM Jobs on WPUse WP Cron for CiviCRM Jobs on WPhttps://lab.civicrm.org/dev/wordpress/-/issues/5Add documentation for shortcodes to help users while waiting for a CiviCRM bl...2021-07-23T06:17:12ZherbdoolAdd documentation for shortcodes to help users while waiting for a CiviCRM block for GutenbergIn the old editor there's a CiviCRM button for adding shortcodes. But in Gutenberg it'll need a different approach. People can add shortcodes but there's not info. I suggest at least adding documentation to help people. Even better if th...In the old editor there's a CiviCRM button for adding shortcodes. But in Gutenberg it'll need a different approach. People can add shortcodes but there's not info. I suggest at least adding documentation to help people. Even better if there's a way to add help text within Gutenberg.https://lab.civicrm.org/dev/wordpress/-/issues/3Create CiviCRM Block for new Gutenberg Editor2023-12-07T22:18:11ZkcristianoCreate CiviCRM Block for new Gutenberg EditorWP is introducing a new editor in v 5.0 - https://github.com/WordPress/gutenberg
As of this post: https://make.wordpress.org/core/2018/07/06/whats-new-in-gutenberg-6th-july/ Gutenberg has been declared to be at the MVP stage and a me...WP is introducing a new editor in v 5.0 - https://github.com/WordPress/gutenberg
As of this post: https://make.wordpress.org/core/2018/07/06/whats-new-in-gutenberg-6th-july/ Gutenberg has been declared to be at the MVP stage and a merge proposal will be submitted "soon". The current target date is "august", but that can move.
Based on the above, it would be a good time to explore what will be needed to convert our CiviCRM shortcode button to a Gutenberg block.https://lab.civicrm.org/dev/wordpress/-/issues/2WordPress Version Update2023-01-25T14:59:09ZkcristianoWordPress Version UpdateCiviCRM files are set to 4.7 in the header blocks on:
- uninstall.php
- civicrm.php
- assets/templates/civicrm.shortcode.php
- includes/civicrm.shortcodes.php
- includes/civicrm.users.php
- includes/civicrm.shortcodes.modal.php
- includ...CiviCRM files are set to 4.7 in the header blocks on:
- uninstall.php
- civicrm.php
- assets/templates/civicrm.shortcode.php
- includes/civicrm.shortcodes.php
- includes/civicrm.users.php
- includes/civicrm.shortcodes.modal.php
- includes/civicrm.basepage.php
- wp-cli/civicrm.php
Is a PR in order or is there a better way to update?
Also
```
// set version here: when it changes, will force JS to reload
define( 'CIVICRM_PLUGIN_VERSION', '4.7' );
```
Needs updating - if a PR is in order we can include this change.https://lab.civicrm.org/dev/wordpress/-/issues/1CiviCRM-WordPress - Gutrenberg Compatibility: Do not parse shortcodes in REST...2023-01-25T14:59:08ZkcristianoCiviCRM-WordPress - Gutrenberg Compatibility: Do not parse shortcodes in REST contextWordPress 5.0 will introduce a new default editing experience. The code name is 'Gutenberg' . Gutenberg is built on blocks and the method of handling modals in the editing experience is changing.
The existing modal for inserting shor...WordPress 5.0 will introduce a new default editing experience. The code name is 'Gutenberg' . Gutenberg is built on blocks and the method of handling modals in the editing experience is changing.
The existing modal for inserting shortcodes will not work with Gutenberg. We will need to rework inserting the shortcode to a new block for the new release. Expected Merge Request for Gutenberg will be April 2018 and the release will be sometime thereafter.
However, this week WP 4.9.5 will ship and in this release will be a call to action to all users to install the Gutenberg plugin to test.
Currently if a CiviCRM shortcode is put into the 'Shortcode Block' there will be an error and the post will not save properly. As [bastienho](https://github.com/bastienho) points out in [PR 126](https://github.com/civicrm/civicrm-wordpress/pull/126) the following error is thrown: ``Notice: Trying to get property of non-object in civicrm/civicrm/CRM/Utils/System/WordPress.php on line 221``
For now we should fix this error and then work on full Gutenberg Compatibility once the official merge request is approved to WP.