Skip to content
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

dev/core#5449 set NOINDEX on non-public event registration pages #31074

Conversation

magnolia61
Copy link
Contributor

Overview

non-public event registration pages are still indexed by search engines
this pr adds a no-index to registration pages for non-public events
Gitlab issue: https://lab.civicrm.org/dev/core/-/issues/5449

Before

non-public event registration pages are still indexed by search engines

After

non-public event registration pages get a NOINDEX metatag in the html header

Comments

A while ago https://issues.civicrm.org/jira/browse/CRM-21639 already added NOINDEX for the event info pages (#11496 & #11498) But this was not done fior the event registration pages. This pr add the same metatag to the event registration pages if the event is a non-pubkic event

Copy link

civibot bot commented Sep 9, 2024

🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷

Introduction for new contributors...
  • If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
  • A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
  • A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
  • If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
  • Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
  • A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
  • To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
  • For more information about contributing, see CONTRIBUTING.md.
Quick links for reviewers...

➡️ Online demo of this PR 🔗

@civibot civibot bot added the master label Sep 9, 2024
Copy link

civibot bot commented Sep 9, 2024

The issue associated with the Pull Request can be viewed at https://lab.civicrm.org/dev/core/-/issues/5449

}

/**
* Assign the minimal set of variables to the template.
*/
public function assignToTemplate() {
//process only primary participant params
$this->_params = $this->get('params');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it was a mistake that this line was moved.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my mistake, thanks for spotting!

@magnolia61 magnolia61 force-pushed the noindex_metatag_for_non-public_event_registration_pages branch 2 times, most recently from ff0e661 to d995c8e Compare September 9, 2024 16:30
@eileenmcnaughton
Copy link
Contributor

@magnolia61 how about this alternative - #31083 - mostly I feel like setting specific default headers is the sort of thing that could change in the future due to an internet change & if that happened we would want to have one function to change

@magnolia61
Copy link
Contributor Author

@magnolia61 how about this alternative - #31083 - mostly I feel like setting specific default headers is the sort of thing that could change in the future due to an internet change & if that happened we would want to have one function to change

Hi Eileen, love this. I'm a very limited coder, just enough to read, understand & tweak what we need. The solution you propose is rocksolid. I think it is really your quality to always look into medium and long-term in civi-development. Thank you for that!

@mattwire
Copy link
Contributor

mattwire commented Oct 8, 2024

Merged via #31083

@mattwire mattwire closed this Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants