Skip to:

Opened 14 years ago

Closed 14 years ago

#1648 closed defect (bug) (fixed)

Deleting Activity leads to 404 (tested in 1.1.1 and 1.1.3)

Reported by: mwollny's profile mwollny Owned by:
Milestone: Priority: major
Severity: Version:
Component: Keywords: activity delete 404


Logged in as Site-Admin, I get DELETE-Buttons on the site-wide activity-stream that link to http://[DOMAIN]/activity/delete/[ACTIVITY-ID]?_wpnonce=[TOKEN]
Logged in as unprivileged user, I get the same DELETE-Buttons on my activities.
Pressing this button in 1.1.1 directly leads to a 404 page. Pressing it in 1.1.3 gives you a confirmation dialog first, then the 404. When you return to the activity page, the activity you wanted to delete is still there.
The issue is reported by several people in the forums:

It seems to affect subdirectory installs. It may or may not affect subdomain-installs - I couldn't really test this. A 404 for the site-wide activity RSS feed is reported along with this issue, though I'd better open a separate ticket for that.

Change History (4)

#1 @jivany
14 years ago

  • Resolution set to worksforme
  • Status changed from new to closed

This has been fixed in the trunk. Works fine on WP 2.9.1 and BP r2398

#2 @jivany
14 years ago

Sorry, works fine in r2389. Having a dyslexic day today I guess. :)

#3 @mwollny
14 years ago

  • Resolution worksforme deleted
  • Status changed from closed to reopened

Sorry for the late reply, I forgot to activate e-mail notifications here. Done that now.

Then this might be about the Wordpress MU Version. We're running 2.8.6; we tried to upgrade to 2.9.1, but there was too much breaking in our install (like activating/reactivating of plugins leading to fatal errors without error details), so we went back to 2.8.6 until some time in the future when we can afford another go at it using BP 1.2.x. Is there a chance to get this working with WP MU 2.8.6? Again, it seems that the error is definitely reproduceable by some other users.

#4 @apeatling
14 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

Sorry, this is not going to get back fixed. It's fixed in 1.2.

Note: See TracTickets for help on using tickets.