After updating PHP to version 7.2 (on Arch Linux) I’ve got the following error message:
Startup failed
Tiny Tiny RSS was unable to start properly. This usually means a misconfiguration or an incomplete upgrade. Please fix errors indicated by the following messages:
FEED_CRYPT_KEY requires mcrypt functions which are not found.
You might want to check tt-rss wiki or the forums for more information. Please search the forums before creating new topic for your question.
PHP says:
PHP Warning: PHP Startup: mcrypt: Unable to initialize module
Does anyone has similar issues and know how to solve it?
do you even have any legit passwords setup for feeds (that are using http authentication)? if not just set crypt key to blank and forget about it, worst case scenario you’ll have to enter your credentials again in the feed editor
also i’m reasonably certain that current master uses PDO for this so you are using some arch-packed code which nobody here is responsible for.
e: mcrypt thing should probably be added to faq since people still can’t figure out searching the forum
Nope, no feeds that actually need passwords. I’ve just updated to the latest version, and tried it again out of curiosity, and get the below error, after a long list of “processing feed id”'s:
PHP Fatal error: Uncaught PDOException: There is no active transaction in <path>/update.php:450
Stack trace:
#0 <path>/update.php(450): PDO->commit()
#1 {main}
thrown in <path>/update.php on line 450
e: re ^: some feed processing had failed. if you can fish out actual SQL error in tt-rss system logs post it here, it might be helpful. should be somewhere before the failed PDO commit.
update.php:445 PDOStatement::execute(): SQLSTATE[22021]: Character not in repertoire: 7 ERROR: invalid byte sequence for encoding "UTF8": 0x89
with the utf8 codes being different for each error message, then at the top there is one E_ERROR (1):
update.php:450 Uncaught PDOException: There is no active transaction in <path>/update.php:450 Stack trace: #0 <path>/update.php(450): PDO->commit() #1 {main} thrown
this is probably related to your unicode problems above. not sure about this, there are known unicode-related issues on mysql (because mysql) but i never ran into any troubles on postgresql.