Hi Lee,

Did you uninstall at General settings -> Plugins?
You should do that at Blog settings -> Widgets. If you remove them there the errors should go.

Good luck

Sorry, not sure I understand what you are asking. Are you asking if I uninstalled the plugin at General settings -> Plugins before removing the widget at Blog settings -> Widgets? If so the answer is no. I didn't uninstall any plugins before removing the widgets. It was a clean install so all I was doing was removing the widgets that are there by default when you create a new blog - Calendar widget, XML links etc.

Sorry if that doesn't answer the question you asked. If it doesn't could you elaborate on what you meant.

Many thanks
Lee

Hi Lee,

You did the right thing. I was suggesting based on the error you got.
Next try uploading every file again to the server. Especially the files in the /inc/ folder.

Good luck

Hi

I have uploaded all the files to the server again and the same thing is happening so no joy there I'm afraid.

I thought I would take a little look in the database to see if the wi_ID that the admin console is looking for is actually in the database and it is all there as far as I can see. The URL for the delete action looks OK (49 is in the widgets table):

/admin.php?ctrl=widgets&action=delete&wi_ID=49

Interestingly though if I click on that link to delete the widget I still get the error displayed but the url in the browser is:

/admin.php?ctrl=widgets&action=delete&wi_ID=49?ctrl=widgets&blog=3

Not sure if that is part of the problem or not but the beginning part of the URL has been duplicated so wi_ID would actually be taken as 49?ctrl=widgets

Am I barking up the wrong tree here?

Lee

Yes, I am running two installations of 2.4.6, and about 80% of the time I get an error message when I remove a widget at blog settings > widgets.

Functions OK, but I have to hit back button on browser and then refresh the screen to show widget removed.

I don't much mind, but it looks really sloppy and might scare a person less hardy/foolhardy than myself--a potential limiter of b2evolution's satisfied users. Or even my choices in recruiting a collaborator to take care of these blogs....

Yeah, mine is the same. It functions fine but shame about the error message. Very true that it would scare people off who don't know that b2evo is far superior.

Lee

Um... I don't see these errors in my v2.4.5 or v2.4.6 installations. And I *always* delete the calendar widget :)

Lemme go double check with an installation I'm always dumping and reinstalling...

Nope. I randomly chose the feeds widget to delete and all it did was tell me, in a green box, the widget was deleted. Must be something funky going on here that needs more research, but off the top of my head I can't think of what.

Okay here's the 64 thousand dollar question: lturner and martha what skin are you using in the back office? I use the 'chicago' one which happens to be default and could be called 'the blue one'. Heck I don't even know what the other skins look like anymore.

I was going to ask lturner to try with a 'stock' skin like evopress or custom but realized it is a back office thing so didn't. Then I remembered the back office is skinned so ...

BTW I can not imagine why a back office skin would be responsible, but hey my 245 and 246 installs don't do this bad thing. So let's just guess!

Hi lturner,

Likely the correct url is

/admin.php?ctrl=widgets&action=delete&wi_ID=49&blog-3

Then this could be an url issue. Did you change anything in blog settings -> Urls?

But the error suggested it went wrong at wi_ID=49. As if the widget is already uninstalled at the time this code is sent.

EdB : I use the chicago skin in the back office so doesn't seem like this could be the problem as you are using that also.

Afwas : I thought the same as you about the correct url. I just added a widget to the sidebar of my skin (so therefore the widget is installed for me to be able to add it) and then deleted it straight away and still got the error so I don't think this is an issue with widgets being uninstalled before being removed from the blog. Doesn't b2evo remove all uses of the widget when a plugin is uninstalled anyway ?

Cheers
Lee

Afwas

I have changed the urls in the blog settings for the three blogs that this is happening on namely to - Extra path on index.php for the blog url and Use extra-path: post title for single posts.

However, I have just created a brand new blog and changed nothing in the url settings and I am still getting the same problem.

Cheers
Lee

lturner would you mind PMing me your admin login credentials and a URL to use them at? I just want to look - I totally promise not to make ANY changes!!!

EdB - Just sent them to you

Cool. It'll take some time as I will be building a brand new 246 installation (without my 'gotta have em' hacks) and duplicating your settings to see if I can duplicate your problem.

This will be very nice as it will take my mind off a very pressing problem: should my plugin promote options based on Group ID or a setting I build into the plugin? I'm on the fence on it ya know? Like, using the Group ID means I can tie all sorts of other stuff to the user. OTOH it means letting some people potentially mess with my group settings. hmmm ....

Give me some time and I'll let you know what I figure out.

EdB wrote:

Cool. It'll take some time as I will be building a brand new 246 installation (without my 'gotta have em' hacks) and duplicating your settings to see if I can duplicate your problem.

This will be very nice as it will take my mind off a very pressing problem: should my plugin promote options based on Group ID or a setting I build into the plugin? I'm on the fence on it ya know? Like, using the Group ID means I can tie all sorts of other stuff to the user. OTOH it means letting some people potentially mess with my group settings. hmmm ....

Give me some time and I'll let you know what I figure out.

Cool thanks for the help

I think I have solved the problem. EdB - I don't suppose you have access to a Safari browser do you? I have just tried the same thing on Firefox on the mac and I don't get the error. I don't have a windows machine so I can't test if it happens on Safari for windows but it certainly does on Safari on the mac.

Lee

Actually I decided to not bother.

You provide no linkback to b2evolution and have the audacity to ask for free help with free software? YOU are the problem!

Hey, hang fire, I am still in the process of developing that skin and it is nowhere near finished. You should get your facts straight before you get on your high horse.

Jesus, give people a chance

Hogwash! Plenty of time to give credit to the initial source of the skin and yourself, but not to the source of the software? Then, before you "get around to it" you come here asking for help and don't even bother to point out you use a POS browser? HOGWASH!

You had your chance when you downloaded a skin from and for a third party and made a point of adding a linkback to your own domain name.

You failed.

Goodbye.

OK, look you can have your opinion and obviously believe what you want to.

I actively promote b2evo everywhere I can because I believe it is the best out there and I have no issue what so ever in linking back to the source. Jesus, I have been developing open source for ages myself. The link back to b2evo will be there when the site is finished but only because the person I am setting the site up for is cool with it. I don't have the luxury of putting it on every site I do as not every client is happy for that to happen. What do I say to them? "Sorry we can't use the best tool out there that I know of as I won't get any help if things go wrong, we best use wordpress instead. It is not as good and it will shaft you in the long term but there you go".

I certainly agree with what you are saying but a different approach is going to be needed moving forwards. A simple question to me and I would have told you exactly what the situation was. I guess you would have still jump to the same conclusion though and still given me a negative vote.

Sorry for not mentioning the browser I was using. If I thought it was relevant it would have obviously been the first thing I mentioned. Personally I see this as a good thing as it appears to have highlighted a solution to a problem that I am obviously not the only one having.

Thanks for your initial interest any way.

OK, well I guess we may as well wrap this up. I have managed to get hold of a windows laptop this morning and install Safari on it and it demonstrates the same behavior. Even though it didn't come to mind at first it seems that the browser is the main factor involved here.

martha - can you confirm if you are using safari or not? If you are then I will add this to the bugs forum, if not then it may be something else.

Cheers
Lee

Hi Lee,

Martha is likely to use Safari (and FF)
Please do report this @bugs.

Thanks