ethercreative
Fatal Error trying to apply Maps update
Description
Status: Forbidden Response: {"error":"User is not permitted to perform this action"}
I've attached the web.log error pertaining to this action. The error is reported on line 3404.
Steps to reproduce
- On a site that has everything apart from Maps fully up-to-date; try to run the Update from Maps 3.5.2 to current Maps release.
Additional info
Application Info
PHP version 7.1.33 OS version Darwin 17.7.0 Database driver & version MySQL 5.5.5 Image driver & version GD 7.1.33 Craft edition & version Craft Pro 3.4.27 Yii version 2.0.35 Twig version 2.12.5 Guzzle version 6.5.5 Imagine version 1.2.3-dev
Plugins
Contact Form 2.2.7 Contact Form Extensions 1.2.1 Dumper 2.0.0 Eager Beaver 1.0.4 Empty Coalesce 1.0.6 Field Manager 2.1.6 Imager v2.4.0 Image Resizer 2.0.9 Inlin 2.1.1 Maps 3.5.2 Minify 1.2.10 Recipe 1.1.3 Redactor 2.6.1 SEOmatic 3.3.8 Similar 1.0.6 Twig Profiler 1.0.1
Modules
my-module modules\Module verbb-base verbb\base\Base
Having exact same issue. Following this.
Heres what my composer looks like:
{ "require": { "craftcms/cms": "^3.4.25", "craftcms/feed-me": "4.2.3", "craftcms/redactor": "2.6.1", "dolphiq/redirect": "1.0.23", "ether/simplemap": "3.5.2", "miranj/craft-obfuscator": "1.0.4", "nystudio107/craft-seomatic": "3.3.8", "pennebaker/craft-architect": "2.3.3", "solspace/craft-freeform": "^3.0.0", "verbb/super-table": "2.5.1", "vlucas/phpdotenv": "^3.4.0" }, "require-dev": { "yiisoft/yii2-shell": "^2.0.3" }, "autoload": { "psr-4": { "modules\\": "modules/" } }, "config": { "sort-packages": true, "optimize-autoloader": true, "platform": { "php": "7.2" } }, "scripts": { "post-root-package-install": [ "@php -r \"file_exists('.env') || copy('.env.example', '.env');\"" ] } }
Kind of uncool to have a site breaking update like this and provide zero response. I realize it's a free plugin, but if you put it out there you really should take ownership. No doubt just having your company name out in the Craft ecosystem can yield positive economic benefits. It can also work the other way too.
This appears to be a permissions issue. Are you running the update while logged in as an account with the correct permissions?
