Tested this on websites reporting the error, but which lacked accounts that differed by upper/lower case characters. Applying the patch resolved the error message on the status page.
My testing was on with mysql databases. Will see if I can setup tests on the others.
Confirmed on latest release, and marking is as fixed.
wylbur → made their first commit to this issue’s fork.
Confirming that the latest merge has resolved this issus. Thanks @yoftahe.addweb for your proposed work here!
Marking this as resolved.
Thanks for this code! We have merged a number of changes, and this was addressed in that merge request. You can test in the latest DEV release.
Marking this as resolved.
Confirming this is resolved with the latest merge request. Marking as fixed.
Tested with latest release, and confirms that long names are not an issue.
Confirming that latest merge fixed my width for diplays without a minimum with specifically set.
Marking this as fixed.
Tested the latest merge request of fixes, and can confirm this resolves the issue.
Confirmed this fix on the latest pull request, this is complete.
Thanks @karlshea, I reviewed your patch and applied to the DEV branch!
wylbur → made their first commit to this issue’s fork.
Confirmed that viewports are NOT created when installing the module via the admin interface instead of Drush.
Proposed solutions
Identify the active theme, and use theme.breakpoints.yml to create viewports
When no theme.breakpoints.yml is present in the default theme:
Install a set of generic viewports for mobile, tablet, desktop
Just confirming this is still an issue with the latest updates.
Closing this ticket as outdated, but please add additional information and reopen if appropriate!
minneapolisdan → credited wylbur → .
minneapolisdan → credited wylbur → .
wylbur → created an issue. See original summary → .
This has been applied, thanks for your help.
We have rewritten this module for the 2.0 release, so this no longer applies. Thanks for your work!
We've rewritten the module for the 2.0 release, so this is no longer applicable. Closing.
Look at Geofield Directions:
https://www.drupal.org/project/getdirections/issues/3398209
📌
Drupal 10 version?
Closed: outdated
Seems to be a good replacement for this functionality.
To get this to work with url query string, you will need to setup a prepopulate, with the prepopulate module:
https://www.drupal.org/project/prepopulate →
Just confirming that the patch in #2 resolves php errors for our install:
drupal 10.3.1
php 8.2
open_readspeaker 1.10.0
Marking this as RTBC.
Also confirming that is the active ticket for the 1.x branch of the module - which is the recommended version at this time.
There is another ticket open covering this for the 8.x-1.0 branch - which is the recommended version!
https://www.drupal.org/project/open_readspeaker/issues/3413732
🐛
Deprecated function: Creation of dynamic property Drupal\open_readspeaker\Plugin\Block\OpenReadspeakerBlock
Needs review
We ran into the same issue today while deploying a site to the LIVE production server. The issue for us was that our deploy process does not run composer install on the LIVE server. This was leaving old files from a previous install of the Gin theme on the server. For us we just removed the table.theme file from the includes folder:
/home/mysite/public_html/web/themes/contrib/gin/includes/table.theme
For others, just remove the gin theme folder and completely reinstall.
Hope this helps others!
My merge commit in #112 applies the patch from comment @93, but now I see that there has been additional work done in later commits. I'll try to add those to the new merge request.
Created a new issue fork with a merge request that applies to Book 1.0 contrib module. Please review.
This applied cleanly to our project:
Drupal 10.3.1
Book 1.0
PHP 8.2
wylbur → made their first commit to this issue’s fork.
wylbur → made their first commit to this issue’s fork.
Confirming that we also experienced this error:
- drupal 10.3.1
- php 8.2
- menu_block 8.x-1.11
Applying the patch resolved the php errors.
Marking this as RTBC
I investigated this issue and this bug still applies.
I tried to create a workaround by adding the fully qualified URL of the site, but on saving the redirect, the fully qualified URL is replaced with the internal node path.
This applies to the latest release and the latest DEV release updated 6 May 2020 at 23:18 UTC.
Marking this as outdated. Please reopen as needed.
Marking this as outdated, and changing from Plan to Documentation. Please reopen if needed.
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!