- Issue created by @rgry
Came across the same issue on drupal 9.4.3. Any chance you've got it fixed already?
- ๐ฌ๐งUnited Kingdom thelinhuk
I am encountering the same issue drupal 10.0.7
I tested on a clean install and didn't see this problem.
Tests configuration:
- Drupal 10.0.7
- restui 1.21.0
- PHP 8.1.11
- ๐ฉ๐ฐDenmark rgry
No longer a problem for my installation with
Drupal 10.0.9
PHP 8.1.18 - ๐ฎ๐ณIndia yashsharma01
It was giving error for me on D10.0.9. I have added to check using class_exists() and working for me.
- last update
over 1 year ago Composer require failure Thanx @yashsharma01 for patch, Patch #10 ๐ TypeError - get_class_methods - php > 8 (drupal 10) RTBC works for me.
- ๐ฎ๐ณIndia rahulk Bangalore
Thank you @yashsharma01. The patch is working for me.
No longer a problem for my installation with Drupal 10.1.1 & PHP 8.1.12
- Status changed to RTBC
about 1 year ago 12:54am 30 October 2023 - ๐ฆ๐บAustralia elc
This is required in a number of situations where the rest resource plugin is "not quite right". This little patch prevents the restui from WSOD while you figure out what has gone wrong. It doesn't seem to be recoverable even after fixing the plugin without this patch. It seems like a very good guard to prevent a fatal error when there is something less than fatal wrong.
- First commit to issue fork.
- ๐ฎ๐ณIndia ankitv18
Currently trying to reproduce this issue on D11 with PHP 8.3
I have simply installed RestUi which enables the RESTFul Web Services.
Below are the methods under the under the EntityResource plugin class.
There might be a reason where rest plugin is not properly configured or outrage of custom rest plugin.
- ๐ฆ๐บAustralia elc
This isn't a day to day error - this happens when you are developing plugin code which uses the restui and you make a mistake. Once it has been triggered, you cannot recover the site unless this code guards against your bad class, which once it is ignored, the caches can be flushed and the fixed class again be shown. Alas, this was so long ago that I can't remembered how I triggered it, but I would suggest adding a new plugin and adding a syntax error to it.
It's a guard against a WSOD - it costs nothing to the codebase - does not present normal use of restui.
It would be ideal if this could be merged in. Perhaps it could log an error so that it's not an invisible fix for a muck up.