Of course you should make sure to back things up before you start testing out deletion scripts right? :)
What is the motivation for this cleanup?
Sorry for the delay in replying, been to busy with other things.
#Matt, yes always backup before doing anything with the database, thanks for the reminder though.
#Evan, the reason for the cleanup. I was running 1.8.11 when I had a crash. I tried many ways to revive the site after the crash and nothing worked. I then went ahead and upgraded to 1.9 to 1.11 one step at a time. I tried restoring the old database but none of the old users could use the site. So, I just left it as is and started over. But all the old data is still on the database. That is slowing down the site. That is why I am trying to cleanup the old data.
By default if things are set to public when you install they will see the activity page.
I'm not familiar with the "Login Redirector" plugin so my first suggestion would to deactivate it and then flush the cache to see what happens.
Same thing happens when I disable "Login Redirector" I always flush the cache when I change a plugin.
Thanks for the suggestion.
Same thing is happening to me with elgg 1.11. I haven't got that plugin installed. I am running elgg in walled garden, should it help.
¿It may have something related to this issue?
https://github.com/Elgg/Elgg/issues/7261
Also, googling, I've seen that this might happen when the favicon is not a public resource, so the browser understands it as the "redirect url" after login. This may happen only on walled gardens.
you'll want to search your files for the embed_init() function. Seems like it must be duplicated somewhere.
It sounds like there are extra plugin references in your database. There are a few ways this could have happened: You appended the old database to the new one, or Elgg's installation directory doesn't or didn't match what's in the database.
Did you follow the instructions for duplicating or restoring an Elgg installation? If you have an unused Elgg installation anywhere on that server, try renaming or removing it.
Brett, you got it. I searched the database for the plugin names and found two references in the "objects_entity" table for each plugin. I removed them and everything is fine now. As I would remove each entry I would do a refresh on the page with the error and it would show an error for the next plugin.
Yes I followed the guide lines as best as I could. My database is so large that I have to break it down into tables and load them one at a time.
Thanks so much for the help and suggestions.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.