🇵🇰Pakistan @Ahmed.Raza

I am facing the exact same error unfortunately links to patches in #4 didn't work for me. Drupal 10.2.6

I was entering wrong path to solr core, please close this. As the issue has been resolved by fixing the path.

By the way I am facing exact same error on local Apache solr configs as well.

Hey @drunken monkey! Here is how it looks like:

Its the same on http with port 80.

ahmed.raza → created an issue.

ahmed.raza → created an issue.

The issue has been resolve in 2.1.0

Again, the issue is not reproducable to me, Checked on fresh drupal installation. The code

`$authenticator->getQr()` returns svg structure, your patch is wrong svg structure cannot be put into .

The issue is not reproducable in the first place. Both of you try reinstalling the module.

Care to explain how/when this error occurs? Also mention your Drupal core version?

I can confirm, I am facing this issue as well with Paragraphs (8.x-1.17) on a Drupal 10 site, reported by the CMS team. See attached below;

I've tested this on fresh Drupal 10 setup and couldn't reproduce. It works as designed.

Need more details on your module and drupal version and steps to reproduce.

Thanks Jaime, though the solution needed some polishing which I've done. The new release 1.0.7 contains this fix.

Couldn't reproduced works as designed.

I tested your solution and it was taking a normal user to admin theme as well. I feel like there is no need for switching themes for anybody in any case in the first place.

ahmed.raza → made their first commit to this issue’s fork.

Tested and working perfectly fine without any crashes or issues.

Thanks

I disagree, this settings page is accessible by the normal users as well which are not admins, setting '_admin_route: TRUE' forces admin theme for everyone including the non-admin users.

I think how it is now is perfect, admins can use the normal site theme its not the end of the world.

Thanks

Sorry for the extremely late response, I was tide up somewhere else. Please update the module to 1.1.3 which includes this fix.

Thanks

@joakland, the module was already enable as it is a common tweaks module serving tweak purpose on various of site hence its already enabled, no offense taken :D

The mistake was I placed this function in the .install file and not in .module file. So I moved it in .module file and ran the drush command to call this function and it worked the error is now gone. Thanks for your help!

@joakland I followed your solution and when running `drush php-eval '_user_update_9301();'` it says;

Error: Call to undefined function _user_update_9301() in eval() (line 1 of /Users/ahmedraza/sites/mysite/vendor/drush/drush/src/Commands/core/PhpCommands.php(30) : eval()'d code) #0 /Users/ahmedraza/sites/mysite/vendor/drush/drush/src/Commands/core/PhpCommands.php(30): eval()

Thanks @larowlan, I think we've met somewhere before on some issue.. xD

Anyways, I've installed the module and here is the diff in detail. It's the column type only which is previously `int` and now wants to be `serial`. So exactly do I fix this?

A little bit of history, the site was originally built in Drupal 8, a few months back it was updated to Drupal 9.something and now its updated to Drupal 10.1.6 and facing getting this error ever since.

Have you searched drupal.org for that message?

Yes @cilefen, found some similar issues but those related to contrib modules that I am not even using.

ahmed.raza → created an issue.

I don't think this should be added back to the core, if it was removed from Drupal 8 upwards, there must have been a good reason for this. I think its best suited to be added via some contrib module. Here I've worked on a small module that provides a formatter from where you can choose which date value to show Start or End date. https://www.drupal.org/project/start_end_date_format →

Thanks much for reporting this issue Aditiya! I've now resolved the issue. The problem was with misconfigured composer.json file of this module. Here in the attached screenshot you can see I freshly installed Drupal 10 and then installed this module on it which is now installed correctly in the web/modules/contrib directory.

Here I've worked on a small module, which basically introduces a new format which has this option dropdown to choose from start or end date to show on the frontend.

https://www.drupal.org/project/start_end_date_format →

Hey @TwoD! Hope you are doing good. It was a server side problem on Dreamhosts. I checked the server error logs and found this;

[Wed Oct 11 05:25:36.454083 2023] [:error] [pid 287740:tid 140662376478272] [client 154.80.43.146:64041] [client 154.80.43.146] ModSecurity: Access denied with code 418 (phase 2). Operator GE matched 7 at TX:anomaly_score. [file "/etc/modsecurity/mod_sec3_CRS/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "93"] [id "949110"] [msg "Inbound Anomaly Score Exceeded (Total Score: 10)"] [severity "CRITICAL"] [ver "OWASP_CRS/3.3.2"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "www.cphrab.ca"] [uri "/wysiwyg/xss"] [unique_id "ZSaUQLBuxxFE87EjI3Z1JACc0iE"], referer:

I contacted Dreamhosts to get it resolved, weird how they decided to throw 418 for this...

Anyways we're all good this can be closed. Thanks

Ahmed.Raza → created an issue.

Hi I am facing the exact same issue where all the site tokens are messed up and also the metatag module page is showing all these metatags in pale yellow background. Previously they were all "Unknown" I cleared the caches and alteast their names came back but when I go ahead and edit any of these their entire form is gone and only "Save" and "Cancel" buttons are available.

Module version: 2.0.26

Getting the exact same error while trying to unpublish a node. Here is the error detail;

ResponseText: The website encountered an unexpected error. Please try again later.Drupal\Core\Entity\EntityStorageException: The state 'archived' does not exist in workflow. in Drupal\Core\Entity\Sql\SqlContentEntityStorage->save() (line 815 of core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php). Drupal\content_moderation\Plugin\WorkflowType\ContentModeration->getState('archived') (Line: 114)
Drupal\content_moderation\EntityOperations->entityPresave(Object) (Line: 104)
content_moderation_entity_presave(Object)
call_user_func_array(Object, Array) (Line: 426)
Drupal\Core\Extension\ModuleHandler->Drupal\Core\Extension\{closure}(Object, 'content_moderation') (Line: 405)
Drupal\Core\Extension\ModuleHandler->invokeAllWith('entity_presave', Object) (Line: 433)
Drupal\Core\Extension\ModuleHandler->invokeAll('entity_presave', Array) (Line: 251)
Drupal\Core\Entity\EntityStorageBase->invokeHook('presave', Object) (Line: 903)
Drupal\Core\Entity\ContentEntityStorageBase->invokeHook('presave', Object) (Line: 563)
Drupal\Core\Entity\EntityStorageBase->doPreSave(Object) (Line: 756)
Drupal\Core\Entity\ContentEntityStorageBase->doPreSave(Object) (Line: 517)
Drupal\Core\Entity\EntityStorageBase->save(Object) (Line: 804)
Drupal\Core\Entity\Sql\SqlContentEntityStorage->save(Object) (Line: 339)
Drupal\Core\Entity\EntityBase->save() (Line: 61)
Drupal\moderated_content_bulk_publish\AdminModeration->unpublish() (Line: 59)
Drupal\moderated_content_bulk_publish\Plugin\Action\UnpublishCurrentRevisionAction->execute(Object) (Line: 22)
Drupal\Core\Action\ActionBase->executeMultiple(Array) (Line: 473)
Drupal\views_bulk_operations\Service\ViewsBulkOperationsActionProcessor->process() (Line: 106)
Drupal\views_bulk_operations\ViewsBulkOperationsBatch::operation(Array, Array) (Line: 295)
_batch_process() (Line: 137)
_batch_do() (Line: 93)
_batch_page(Object) (Line: 55)
Drupal\system\Controller\BatchController->batchPage(Object)
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 169)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 53)
Asm89\Stack\Cors->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 718)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

Hi dianacastillo, I know its super long time ago but by any chance do you remember how did you achieve this? I am facing similar problem any help will be highly appreciated.

Hi guys here are the files from custom solution in case someone is looking the same thing.

Place "OfficeHours.php" inside 'src/Plugin/views/field/' of your custom mdoule and "mymodule.views.inc" inside your custom modules' root folder. Make the appropriate changes as per your needs clear the caches and you should be good to go.

Thanks

@ressa, actually there are two issues already created there;

https://github.com/hechoendrupal/drupal-console/issues/4345
https://github.com/hechoendrupal/drupal-console/issues/4344

I am amazed, how a team built something this amazing and then just went missing. There is no support for Drupal 9 and above and people have been complaining for this for a long time now. Anyways lets try to "+1" above issues on github issue queue.

Thanks

+1

@xmacinfo: Agreed! Drupal 7 has still the biggest market share on all current Drupal sites. It should be supported indefinitely until less than 10 % of Drupal sites are still on Drupal 7 or lower.

Keeping the EOL as is will hurt the Drupal community and make many Drupal 7 sites will be side-graded to other CMS, or platforms, instead of being upgraded to Drupal 9/10.

110% agreed on the later part. This is already happening in my firm, there is 5 years of efforts in making a multi-millionaire project in Drupal 7 and there is already planning undergo as the Drupal 7 support is going to end so this is the best time and lets rebuild this project in ROR or some other framework.

Hi Johnv, I ended up writing my own Views field plugin and rendering the hours information for each day of the week in its own column. But it'd be great to have separate fields in the Views and this is something doable, an example is the popular Address → field module. This is a should have in case you want to export the data into a CSV for example Google Business that was the case for us we had to export the data into a specific format which required us to have these opening and closing hours information of each day of the week into its own column within the CSV. We were using views_data_export to generate the CSV but had no way to showing hours of each day into their separate columns.

My custom solution:

Address module fields:

Hi @johnv, we need the ability to show days like this on a Views table. Basically each day of the week showing its hours in individual column.

Please update to 2.0.7, this issue has been resolved in that release.

Drush reset command has been added and will be part of a future release.

Thank everybody for sharing the patch, I was using exactly same approach to render the QR previously, don't remember what made me change it to FormattableMarkup. Anyways I am merging the patch by @bharath-kondeti.

Ahmed.Raza → created an issue.

I am sorry, couldn't get it. What exactly that drush command will do?

Ahmed.Raza → created an issue.

Sidharth thank you for reporting this and bringing this to my attention and for your time on resolving the issue. I have also resolved the dependency injection issues in the files and resolved a few other phpcs related issues such as doc blocks etc. You can update your module to 1.1.2 which contains these phpcs fixes. Thanks

1.1.1 version provides site administrators to check whether to allow users to enable/disable 2FA via email or not.

1.1.1 version provides site administrators to check whether to allow users to enable/disable 2FA via email or not.

Ahmed.Raza → created an issue.