We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hei there.
When I did a fresh install in Craft 4 on php 8.1.12 I got the following error when I tried to view the settings:
/admin/settings/plugins/craftagram
scaramangagency\craftagram\Craftagram::getSettingsResponse(): Return value must be of type mixed, none returned
in line 151
public function getSettingsResponse(): mixed { Craft::$app->controller->redirect(UrlHelper::cpUrl('craftagram/settings')); }
The site is on Craft 4.3.6.1, php 8.1.12 and the plugin is 2.0.1.
The text was updated successfully, but these errors were encountered:
Also seeing this error on PHP 8.1, latest versions of Craft and Plugin, unable to install.
Sorry, something went wrong.
OK, I discovered by uninstalling and reinstalling via the CP that there is a URL issue.
It looks like the two CP links to settings, linked in the logo icon here:
And "settings" text here:
...both link to the wrong place.
The both link to: /admin/settings/plugins/craftagram.
If you install via command line, you only ever see links to this broken URL.
Whereas, if you install via CP, after installation you are automatically taken to /admin/craftagram/settings/1?site, which appears to work OK.
/admin/craftagram/settings/1?site
Hope this is helpful!
Fixed in 2.0.2
No branches or pull requests
Hei there.
When I did a fresh install in Craft 4 on php 8.1.12 I got the following error when I tried to view the settings:
/admin/settings/plugins/craftagram
scaramangagency\craftagram\Craftagram::getSettingsResponse(): Return value must be of type mixed, none returned
in line 151
The site is on Craft 4.3.6.1, php 8.1.12 and the plugin is 2.0.1.
The text was updated successfully, but these errors were encountered: