Marking this issue as a duplicate. The related issue does have fix which has been committed to the 7.x-2.x branch - but that branch is deprecated.
Marking this issue as outdated. The comments also point to using the Path Redirect Import module for importing redirects. Please reopen if needed.
Marking this as outdated, please reopen if needed!
Marking this as outdated. Please reopen if needed.
Marking this as outdated. I ran the tests as indicated in the ticket, and did not find any of the ambiguous test values listed above. Please reopen with current updated information if needed.
Marking this as outdated for now. If you have suggestions for help text please reopen this ticket.
Marking this as outdated. Please do add separate feature requests if you are able.
Marking this issue as outdated. Please reopen with more information if needed.
The redirect works when domain access is not involved. The module listed above provides an option for creating domain specific redirects, so marking this as works as designed.
Based on the comments, marking this as resolved.
Since the module is working, and this report does not indicate otherwise, I am marking this as closed - won't fix. Please reopen if there is an issue with the operations of the module.
Patches are also welcome.
Checked the current code, and similar changes have been made to this module already. Please take a look at the current version and reopen this ticket as needed.
Marking this as outdated.
Checking on the latest release shows that this fix has already been applied. The value of $conf['page_cache_invoke_hooks'] is being displayed on the settings page.
Marking this as fixed.
Since there is a viable solution in comment #1, marking this issue as closed (works as designed).
Closing as outdated.
Marking this as outdated. The maintainer has also indicated that this actionable that this time.
Let's mark this as outdated, but please reopen if needed.
Closing this as outdated, please reopen if needed and provide more details about the warnings you are seeing.
wylbur → changed the visibility of the branch 3402972-2.1.x to hidden.
wylbur → made their first commit to this issue’s fork.
@minneapolisdan
Today I made the following updates:
- Updated the speaker teaser display to show summary or trimmed instead of default body content
- Updated the speaker teaser twig template to show the title as link, but only if the link field is provided
These changes have been pushed to the LIVE site. If you want to remove the link from the current speaker you can, but I did not change anything.
Let me know if we need anything else!
wylbur → made their first commit to this issue’s fork.
I found this issue from a google search for the error message. My issue persisted, even after applying the patch. Since I was testing patches, I started over with a fresh install on a clean D10 site. No issues after the fresh install.
I received that error after trying to create new groups. The install process never completed after each group install. Each time I ran the install, it would return to the group page, with no installs, and the same number of error messages for each attempt I had made. It seemed clear that the system was creating groups, but hanging on each install. Each of these hung installs created another entity that caused an error. In my case the patch never resolved the issue or suppressed the errors.
Not a solution, but hope this helps someone else trying to diagnose this.
I added a not in the README.md file, and a link pointing back to this issue - #3230990.
Today I created a merge request that updated the patch, and reformatted the readme into a markdown file that follows current Drupal best practices. Thanks to @amjad1233 for the initial patch!
wylbur → made their first commit to this issue’s fork.
Based on the comments, marking as needs work.
wylbur → changed the visibility of the branch project-update-bot-only to hidden.
I'll add another request for this feature. If you are adding webforms to nodes via layout builder, blocks, paragraphs, the webform ID changes:
form id - webform_submission_contact_add_form
becomes
formid - webform_submission_contact_node_20139_add_form
For now, we are enabling captcha on all forms, and setting permissions that all authenticated users can skip captchas.
@ultrabob, after spending some time trying to get test working, I totally agree with you! I'll create a new issue, and work on some fixes. Let's stick with deleting tests here, and working on this on a new issue. I'm marking this as RTBC, but let me know if this needs more input.
Thanks!
Thanks for your feedback Dan I am marking this as Fixed.
This issue needs test coverage, I will see what I can do!
I reviewed the issue and code.
The .gitlab-ci.yml looks good, I ran it through cs-lint on gitlab, and it passed.
Status:
Syntax is correct. CI configuration validated, including all configuration added with the include keyword.
I did have a question about the commit to "Remove test files that are not testing Workflow Buttons functionality" - did you intent to remove all the test files?
Will leave this issue as needs review. Let me know if there are other actions that need to be done to verify this issue.
This has been setup today, and configured. I will share the credentials with the group in a google doc.
wylbur → created an issue.
The news page, and content are ready for review on the LIVE site. Who else should review this?
Newsletter page has been added, with a link to the Mailchimp signup page.
https://2024.twincitiesdrupal.org/join-our-newsletter
Please test @minneapolisdan !
We are using the Registration Role module. This defines a NEW ROLE that is assigned to users that self-register. We use this role to give them permission to create sessions.
Because we are using this, we need the speaker role to allow new users to create content.
If this does NOT work as it did last year, please let us know!
Does the redirect work if the overlay is omitted?
Marking this issue as outdated. Please reopen if needed.
Marking this issue as outdated. Please reopen if needed.
You have some options. Use Views Bulk Operations to pick which nodes to update.
Marking this issue as outdated. Please reopen if needed.
Marking this issue as outdated. Please reopen if needed.
Is this still an issue? I just tested, and adding a url with a slash at the end - the slash is removed.
Marking this issue as outdated. Please reopen if needed.
Marking this issue as outdated. Please reopen if needed.
Marking this issue as outdated. The presence of https is ubiquitous now, so closing this as outdated.
Updating the title, and changing this to a feature request.
Marking this issue as outdated. Please reopen if needed.
Marking this as a feature request.
Marking this issue as outdated. Please reopen if needed.
Marking this issue as outdated. Please reopen if needed.
Marking this as outdated. Please reopen if needed.
Marking this as resolved.
Marking this as a feature request as this is not implemented in the 7.x version at this time.
Marking as outdated, please reopen if needed.
Marking is as outdated, reopen if needed.
Thanks for sharing this. Since you submitted this patch we don't see any comments about others using this feature. We will mark this as outdated, but it will still be available as a closed issue.
I'm marking this as outdated, but is you still need help, please reopen with more info.
Take a look at the referenced issue #2760089: Is $conf['page_cache_invoke_hooks']=TRUE really required for Redirect cache? → , marking this as outdated.
The referenced issue #1263884: Avoid redirect field and form injection on entities that have a path but where this makes no sense (like comments) → has been resolved, so marking this as a duplicate and closing.
I'm marking this issue as outdated. It appears you already found a solution to your issue, but please do reopen if needed and add more details.
Marking this as outdated.
Marking this as works as designed.
Marking this as works as designed.
Marking this as outdated.
Marking this as a feature request. Would this be something that should be handled in documentation?
Marking this as resolved in #1250710.
Marking this as closed (outdated).
Closing this, as resolved.
minneapolisdan → credited wylbur → .
andrewozone → credited wylbur → .
Marking this issue as outdated, as we prepare for D11 compatibility!
Today I tested the automated Drupal 11 compatibility fixes. I installed the module with the fixes on a D11 dev site, and visually tested the module. While placing blocks with default values, the exposed defaults were available.
I also ran phpunit tests, which passed.
I updated the vbnefd_test_config_info.yml file, adding project names to views dependencies. This also passed phpunit testing.
One question, do you want to continue to provide support of Drupal 8 and 9? The current version supports ^8 || ^9 || ^10, while the proposed version is just ^10 || ^11. This could be addressed with a new major version instead of another rc release. That's more of a style issue up to the maintainers.
Ready for review.
wylbur → made their first commit to this issue’s fork.
wylbur → created an issue.
This has been added and is available for testing on the LIVE site.
This is completed, so marking this as fixed.