Something went wrong while trying to remove deleted documents

LAMP 0.9.6.1p2 install. When utilizing "purge deleted documents" button I receive the following error and documents are not purged:

"Something went wrong while trying to remove deleted documents!"

Can someone point me in the right direction? My searches proved fruitless but the obvious is almost always nearby. ;-)

Thanks!

-Greg

Maybe you’ve duplicated a folder including documents with aliases filled in while you don’t use FURL? Then you run into this issue. Rename all double aliases and you can remove deleted docs.

Thanks for your input. We’ll try that and report back with our results.

Thanks again.

-Greg

I am getting the same error. I havent duplicated any folders what would the aliases have to do with deleting a record with a unique ID?

On line 43 of file manager/processors/remove_content_processsor.php substitute


for the existing error echo, at least you’ll be able to see what MYSQL thinks of things here.

Heres what I get. Can’t make heads nor tails of it though.


Warning: mysql_error(): supplied argument is not a valid MySQL-Link resource in /nfs/c03/h02/mnt/51662/domains/domesticviolencecenter.org/html/manager/processors/remove_content.processor.php on line 43

So I deleted the document, then purged the deleted documents (which threw the error) then hit refresh in my browser and it disappeared from the tree. Took a look at the db itself and its removed from there as well.

hmmmm.....tried it again and what I posted above didnt work. I thought it might be the FURL auto alias generation.

I took your advice and attempted to change the alias and title to another name and, when saving the revised file I receive:

An error occured while attempting to save the edited document. The generated SQL is: UPDATE `db18981_bcmodx`.`db18981_bcmodxsite_content` SET introtext=’’, content=’
\r\nSOME TEXT

[CONTENTS OF DOCUMENT CONTENT]...

, pagetitle=’Brand Expression | Article-2’, longtitle=’’, type=’document’, description=’’, alias=’brand-2’, link_attributes=’’, isfolder=0, richtext=1, published=1, pub_date=0, unpub_date=0, parent=63, template=4, menuindex=’1’, searchable=1, cacheable=0, editedby=2, editedon=1223993649, publishedon=publishedon, publishedby=publishedby, contentType=’text/html’, content_dispo=’0’, donthit=’0’, menutitle=’Brand Expression-2’, hidemenu=’0’ WHERE id=28; .
Warning: Cannot modify header information - headers already sent by (output started at /home/18981/domains/blackcoffee.com/html/inhouse/litho/manager/processors/save_content.processor.php:442) in /home/18981/domains/blackcoffee.com/html/inhouse/litho/manager/processors/save_content.processor.php on line 576

I revised the template and eliminated most of the content, changed alias, title, etc to avoid conflict and received the following error while saving the revised file:

An error occured while attempting to save the edited document. The generated SQL is: UPDATE `db18981_bcmodx`.`db18981_mydatabase_content` SET introtext=’’, content=’’, pagetitle=’junk’, longtitle=’’, type=’document’, description=’’, alias=’junk’, link_attributes=’’, isfolder=0, richtext=1, published=0, pub_date=0, unpub_date=0, parent=63, template=3, menuindex=’1’, searchable=1, cacheable=0, editedby=2, editedon=1223997552, publishedon=0, publishedby=0, contentType=’text/html’, content_dispo=’0’, donthit=’0’, menutitle=’junk’, hidemenu=’1’ WHERE id=28; .
Warning: Cannot modify header information - headers already sent by (output started at /home/18981/domains/awebsitedomain.com/html/directory/subdirectory/manager/processors/save_content.processor.php:442) in /home/18981/domains/awebsitedomain.com/html/directory/subdirectory/manager/processors/save_content.processor.php on line 576

Any thoughts on this one?

Thanks for your help.

-Greg

I pulled out the error sql command and used a straight mysql_error() and it returned this:

Incorrect key file for table ’modx_site_content’; try to repair it.

I am using sql 4.1.11 btw

So with that info I repaired the table modx_site_content and everything is working again. Maybe try checking your table and see if theres something fishy at that level?

Repairing the site_content table did the trick. Bang. Files gone.

Thanks a million!

-Greg