-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
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
SEOmatic 5 b5, failed sitemap generation queue jobs #1425
Comments
Do you happen to have a stack trace? It should be in |
Well, trying to look at the log froze my PHPStorm, but switching to VSCode... here's everything from the log that has the matching timestamp:
|
hmmmm yeah there's nothing showing the stack trace for the error in there. Perhaps it's in another one of your log files? |
Ahhhh, this might be more like it!
|
Sadly, no... that's just pointing out some model validation errors. Happy to do a screen share with you at some point to try to get to the bottom of it if you like. |
I'll try a proper clear out of logs and get it to regenerate the error. I thought I was just being ignorant, but yeah it didn't look like there was any real error to me either. |
OK, so I wiped the log files and then:
It results in the "Failed Jobs" icon, with that original error from above. Here are the complete log files for that: |
There isn't an |
Nope, that was literally "empty the storage/logs directory out, save the entry, and then those two files were the only things in the directory after. No phperror.log or anything else. It's an odd one. |
Here's a database dump and composer files just in case. I'm still consistently getting the issue - very weird. (Zip because GitHub was eating the raw lock file). |
I get this error using your db dump:
...attempting to fix... |
Odd. This is a project entirely done in DDEV and from scratch with the Craft5 beta 1. You want a fresh export?
is the DDEV config. |
I got the project up and running by doing a search and replace in the db dump to change the collation from For whatever reason, the error reporting isn't happening, the exception isn't logged in I was able to get a stack trace by running the CLI command
|
Addressed in the above commits Craft CMS 3: You can try it now by setting your semver in your "nystudio107/craft-seomatic": "dev-develop as 3.4.73”, Then do a ….. Craft CMS 4: You can try it now by setting your semver in your "nystudio107/craft-seomatic": "dev-develop-v4 as 4.0.43”, Then do a ….. Craft CMS 5: You can try it now by setting your semver in your "nystudio107/craft-seomatic": "dev-develop-v5 as 5.0.0-beta.6”, Then do a |
Just seen this after the b6 got installed... seems fixed, thanks Andrew! |
Discovered this, this morning, FYI... |
Describe the bug
Getting a few of these stacking up in the Queue.
Too few arguments to function craft\base\Element::get(), 0 passed in /var/www/html/vendor/yiisoft/yii2/base/Component.php on line 231 and exactly 1 expected
To reproduce
Steps to reproduce the behaviour:
Screenshots
The text was updated successfully, but these errors were encountered: