Hi;
I was working through the tut "Creating a blog in Revo" and every time I loaded the site it crashed with a fatal error. By commenting out the blog template code, bit by bit, I narrowed it down to any time Quip was called. If I commented out the quip calls, the site runs ok (on XAAMP). I decided that Quip might be corrupt or not installed completely. (I’m running with MODx Revolution 2.0.0-pl rev7212) Evidently quip never installed properly on the initial install of Revo.
In the package management, I ran the uninstall on quip and got an error message - it could not uninstall it.
OK so I downloaded a new copy of quip 2.0.1, however Package Management still shows quip installed and does not give an install option.
In the MODx manager>files>components; quip is not showing.
How do I re-install a new copy of quip if package management thinks quip is still installed?
Thanks.
"Today’s headlines are nothing more than whispers of history"
alexm;
I was leaning in that direction - but your tip pushed me into doing it.
The blog template works ok now with no fatal errors.
Don’t really know what the problem was, but my installation of quip was probably corrupted.
Thanks,
HalD
"Today’s headlines are nothing more than whispers of history"
I'm struggling with almost the same problem.
I got spammed by bots, and while I was solving this, I chose to upgrade from Quip 2.3.2 to 2.3.3.
Upgrade went wrong. New-posted comments do no more appear on the front-end, but they are stored in the db. Old comments and the reply form are still in place on the front-end.
I chose to uninstall the whole stuff and re-do the entire thing, with a fresh Quip install.
Now I can't uninstall Quip anymore, cf attached file.
The Quip component stays in the back-end Component menu. It appears as "not installed" in the package management. I just feel like doomed, I can't handle this alone. Can someone help me please ?
Revo 2.2.4
PS : after some Quip uninstall attempt, I reran the whole system setup, which was ok, but nothing changed about the Quip component.
Sorry for that ⇧ , I'm no dev but I wanna try
I'm pretty sure you can't uninstall Quip if you're using Articles, without uninstalling Articles first (since it's a combined packaged). If you're not using Articles, can you not "Force Removal" of the package?
Garret Overstreet
Business and Marketing Consultant
I'm not using Articles, and tried to force removal of each package (current and older ones) - the removals actually worked, more or less,
what happens is that I get that crappy "Unexpected Token, Internal Server Error" message for several times now.
And after I clean the system at my best, this is what I get when i try a brand new fresh Quip installation :
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => quip.emailsFrom )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => quip.emails_from_name )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => quip.emailsTo )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => quip.emailsReplyTo )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => quip.allowed_tags )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => recaptcha.public_key )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => recaptcha.private_key )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => recaptcha.use_ssl )
Skipping vehicle object of class modPluginEvent (data object exists and cannot be upgraded); criteria: Array ( [pluginid] => 17 [event] => OnEmptyTrash )
Attempting to preserve files at /var/www/vhosts/swqw.fr/httpdocs/core/components/quip into archive /var/www/vhosts/swqw.fr/httpdocs/core/packages/quip-2.3.3-pl/modCategory/5888e14b1c8e5c8ae6c287c24a9db855.0.preserved.zip
Attempting to preserve files at /var/www/vhosts/swqw.fr/httpdocs/assets/components/quip into archive /var/www/vhosts/swqw.fr/httpdocs/core/packages/quip-2.3.3-pl/modCategory/5888e14b1c8e5c8ae6c287c24a9db855.1.preserved.zip
Error adding field quipComment->name: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'name' )
Error adding field quipComment->email: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'email' )
Error adding field quipComment->website: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'website' )
Error adding field quipComment->resource: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'resource' )
Error adding field quipComment->idprefix: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'idprefix' )
Error adding field quipComment->existing_params: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'existing_params' )
Error adding index resource to quipComment: Array ( [0] => 42000 [1] => 1061 [2] => Duplicate key name 'resource' )
Error adding field quipComment->ip: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'ip' )
Error adding field quipComment->rank: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'rank' )
Error adding field quipComment->approvedby: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'approvedby' )
Error adding field quipComment->deleted: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'deleted' )
Error adding field quipComment->deletedon: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'deletedon' )
Error adding field quipComment->deletedby: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'deletedby' )
Error adding index approvedby to quipComment: Array ( [0] => 42000 [1] => 1061 [2] => Duplicate key name 'approvedby' )
Error adding index deleted to quipComment: Array ( [0] => 42000 [1] => 1061 [2] => Duplicate key name 'deleted' )
Error adding index deletedby to quipComment: Array ( [0] => 42000 [1] => 1061 [2] => Duplicate key name 'deletedby' )
Error adding field quipThread->quip_call_params: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'quip_call_params' )
Error adding field quipThread->quipreply_call_params: Array ( [0] => 42S21 [1] => 1060 [2] => Duplicate column name 'quipreply_call_params' )
Could not load class: quipNotifyComment from mysql.quipnotifycomment.
Could not load class: quipNotifyComment from mysql.quipnotifycomment
what about those columns duplications ? what am I supposed to clean to wipe those messages out ?
Sorry for that ⇧ , I'm no dev but I wanna try
I'm back there again to apologize for having been so careless : I actually had Articles installed.
So that's my situation.
- I had Articles installed
- Forgetting that, I tried to uninstall Quip.
- Several error messages appeared in the manager, including "Unexpected Token, Internal Server Error..." and red lines about duplicated columns etc...
- Quip appeared then as uninstalled in the packages manager BUT was still working on the front-end, except that the new-posted comments did not appear on the front-end (but were stored in the db, appeared in the backend).
- I tried to uninstall/force remove/rerun modx setup/reinstall Quip, i Tried to uninstall Articles and reinstall each needed add-on one by one, there's no solution :
Articles' uninstall log blinks red of errors, Quip keeps bleeding red of errors, if I could I'd say that it's all fµ*##d up. Can someone tell me how I could clean or nuke everything that concerns Articles or Quip so that I can reinstall one of them in a proper way and make my (production) website work again ? I beg for your help... thank you a lot
Sorry for that ⇧ , I'm no dev but I wanna try
A bit more info : as I said, the comments are posted in the db and in the Quip Manager but don't appear on the frond-end.
Modx Error Log shows :
[2013-02-05 17:45:31] (ERROR @ /index.php) [Quip] Thread not found for comment: Array
(
[id] => 4
[thread] => Evoken-AtraMors-thread
[parent] => 0
[rank] => 0000000004
[author] => 1
[body] => fghfgdummycontent
[createdon] => 2013-02-05 17:45:31
[editedon] =>
[approved] => 1
[approvedon] =>
[approvedby] => 0
[name] => kehezen
[email] => (my email)
[website] => h
[ip] => (my ip adress)
[deleted] =>
[deletedon] =>
[deletedby] => 0
[resource] => 68
[idprefix] => qcom
[existing_params] => Array
(
[a] => 47
)
[nospam] =>
[auth_nonce] =>
[preview_mode] =>
[comment] => fghfgdummycontent
[quip-post] => 1
)
so what can I conclude ? sorry for asking but I'm helpless
Sorry for that ⇧ , I'm no dev but I wanna try
Quote from: kehezen at Jan 29, 2013, 04:15 AMI'm struggling with almost the same problem.
I got spammed by bots, and while I was solving this, I chose to upgrade from Quip 2.3.2 to 2.3.3.
Upgrade went wrong. New-posted comments do no more appear on the front-end, but they are stored in the db. Old comments and the reply form are still in place on the front-end.
I chose to uninstall the whole stuff and re-do the entire thing, with a fresh Quip install.
Now I can't uninstall Quip anymore, cf attached file.
The Quip component stays in the back-end Component menu. It appears as "not installed" in the package management. I just feel like doomed, I can't handle this alone. Can someone help me please ?
Revo 2.2.4
PS : after some Quip uninstall attempt, I reran the whole system setup, which was ok, but nothing changed about the Quip component.
It sounds like your database is missing tables, or you're trying to overwrite them. Make sure you have a backup of your table with all the tables, then create a fresh install, without any add-ons. If your database has the addons, be sure to remove them after importing your database After reimporting your database (and making sure you have no packages installed), THEN install your add-ons afterward. I've ran into the problem before where it thinks I have everything installed, from an imported database, but it's missing the files, because they weren't properly installed. The console will likely give you errors since the tables are already created, but be sure to look over phpMyAdmin... because it sounds like you're trying to call something that isn't physically there (hence the array errors.)
Garret Overstreet
Business and Marketing Consultant
To completely remove a package, you have to do uninstall, then remove, once for each version you've installed until it no longer shows in the tree.
Even then, there can sometimes be leftover pieces of the package in the DB (particularly in the System Settings table -- and of course, the cache). You may have to delete them manually.
