search

aaron13100 / 404solution

404 Solution
https://ajexperience.com/wealthpsychology/404-solution/
4 stars 2 forks source link

Move ALL Captured 404 URLs to Trash #8

Closed aaron13100 closed 7 years ago

aaron13100 commented 7 years ago

From @fdeitelhoff on July 3, 2016 19:21

What I Expected To Happen

A new button in the "Captured 404 URLs" tab would be awesome that moves all captured 404 urls to the trash.

What Happened Instead

I have to select them manually one by one and moving them just in 25er batches. And this time I have 297 pages of captured urls to this is a huge time waste.

_Copied from original issue: ThemeMix/redirectioner

aaron13100 commented 7 years ago

From @defries on July 6, 2016 11:6

Thanks for reporting @fdeitelhoff. Sounds like a solid feature and we'll look into it how to best approach this.

aaron13100 commented 7 years ago

This is corrected with the future release of version 1.6.5 by adding the "All" option to the "rows per page" option on the Captured 404s page. As a workaround for the current version, open the Captured 404s page, then add &perpage=10000 to the URL and press enter.

fdeitelhoff commented 7 years ago

@aaron13100 Many, many thanks!

remkus commented 7 years ago

Out of curiosity, Aaron, why did you opt for a full fork instead of a pull request and help us fix the one we took over?

On 7 April 2017 at 16:46:27, Fabian Deitelhoff (notifications@github.com) wrote:

@aaron13100 https://github.com/aaron13100 Many, many thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aaron13100/404solution/issues/8#issuecomment-292556853, or mute the thread https://github.com/notifications/unsubscribe-auth/AAZHhKnN1wBFsYQcuEZfgDHWqJ4JNCbQks5rtkxDgaJpZM4MCvt6 .

aaron13100 commented 7 years ago

Hey defries! Thanks for stopping by. "Personal reasons." I know it generally doesn't make sense to create yet another new plugin when there's already one out there, because who needs 100 plugins that do exactly the same thing, right? But there are a few reasons. It looks like the original is going towards a "pro" vs "free" model that I wouldn't be able to profit from (based on the issue labels). I want to have full control over the functionality decisions because I think it's more fun that way. And I want to be able to add a link directly to my website somewhere in the plugin, which wouldn't really make sense being only a contributer and not the owner.

Those three reasons, plus what seems like not that much activity on the original. I had a cruddy experience with a completely unrelated plugin, contributing my time only to have my work virtually ignored (https://github.com/essiembre/eclipse-rbe/pull/48). So I also wanted to avoid that possibility as well.

I figured it didn't make any sense to ask for everything I wanted above without having "proven myself." No hard feelings I hope.

-Aaron

remkus commented 7 years ago

No hard feelings, but you could've asked first what our stance and plans are :)

On 7 April 2017 at 23:31:33, Aaron (notifications@github.com) wrote:

Hey defries! Thanks for stopping by. "Personal reasons." I know it generally doesn't make sense to create yet another new plugin when there's already one out there, because who needs 100 plugins that do exactly the same thing, right? But there are a few reasons. It looks like the original is going towards a "pro" vs "free" model that I wouldn't be able to profit from (based on the issue labels). I want to have full control over the functionality decisions because I think it's more fun that way. And I want to be able to add a link directly to my website somewhere in the plugin, which wouldn't really make sense being only a contributer and not the owner.

Those three reasons, plus what seems like not that much activity on the original. I had a cruddy experience with a completely unrelated plugin, contributing my time only to have my work virtually ignored ( essiembre/eclipse-rbe#48 https://github.com/essiembre/eclipse-rbe/pull/48). So I also wanted to avoid that possibility as well.

I figured it didn't make any sense to ask for everything I wanted above without having "proven myself." No hard feelings I hope.

-Aaron

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aaron13100/404solution/issues/8#issuecomment-292656950, or mute the thread https://github.com/notifications/unsubscribe-auth/AAZHhAHhWeVANeJhdSsU3LZFS2pEIolRks5rtqs1gaJpZM4MCvt6 .

aaron13100 commented 7 years ago

Yeah, you're right. Honestly I was hoping you wouldn't notice and I didn't know the issues would be linked forever when I copied them. I'll close and recreate the related tickets so you guys won't be bothered anymore.

What are your stance and plans on the issue, by the way?

remkus commented 7 years ago

We are working on a complete and full rewrite. The current code is just not up to spec for high-performance sites, nor is it stable enough to use to expand on.

On 9 April 2017 at 10:18:46, Aaron (notifications@github.com) wrote:

Yeah, you're right. Honestly I was hoping you wouldn't notice and I didn't know the issues would be linked forever when I copied them. I'll close and recreate the related tickets so you guys won't be bothered anymore.

What are your stance and plans on the issue, by the way?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aaron13100/404solution/issues/8#issuecomment-292771727, or mute the thread https://github.com/notifications/unsubscribe-auth/AAZHhOZ1sYFM5DOafR4UNb4fuL611jHZks5ruJRmgaJpZM4MCvt6 .