-
Notifications
You must be signed in to change notification settings - Fork 13
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
Cronjob PHP Warning #32
Comments
Would you mind trying to get the stack trace to know at which point the error is thrown? |
Sorry, I'm not a developer, so I do not know how to do that. With a detailed guide, I would possibly do it. Altervativ I can also give you access to the TYPO3. |
Access to the TYPO3 would help. |
Yes I have, message is out now. |
Is there a solution by now? |
Hello Chegaro, thanks a lot for your merge request. I'll have a look at it, as soon as possible. Edit: This issue will be fixed in the next release, as I'm removing the whole folder dependency in both Command and Service. I still have to do a few tests with Amazon CDN as this wasn't working with the change and setting up a testing environment is a bit tricky. See #27 Edit 2: Meanwhile you could load version dev-develop if you don't use Amazon CDN, which now comes with this bugfix. |
I tried the dev version. The following error message appears:
|
Was the close a missclick or is the problem solved? So you are running a Composer based setup right? |
The problem based on commit #33 |
Did you update via composer or just downloaded and replaced it on the server? |
I have updated the develop branch. Running tinyimg on a composer based setup works now like a charm for me. |
Version 1.3.0 is released now. Support for non composer setup has been dropped. Developers have to take care of installing the tinify library themself if the extension is installed via the extension manager. |
Ich bekomme beim ausführen diese Fehlermeldung:
The text was updated successfully, but these errors were encountered: