[07-MAR-2016] Current status of BLF upgrade process

Actually I was meaning to ask you what the !important does, I’ve never seen that before.

It’s definitely easier to hide it. :slight_smile: That div seems to come from a different module, and I prefer to make all the changes in one spot wherever possible.

How’s it look now?

:beer: :beer:

Better. Thank you Sb!

Is there plans to bring back the mouseover ability?

Yep, it’s the last (and next) item on the todo list.

cool, i should have checked that before asking :blush:

Edit: We need a new smiley, is there a homer simpson d’oh smiley available?

Greetings & Salutations SB,

In BLF's previous incarnation, we could select in Settings whether we wanted to use the Advanced Post Editor or the Simple Post Editor by default when posting.

Any chance of bringing this setting back? As right now there is no choice, & the default is the Simple Post Editor.

Thank you Very Much for all you are doing for us. GREATLY Appreciated.

Best Regards,

George

I feel bad adding to SBs workload but links are not posting properly like they used to with the new software :frowning:

an example

Ok, a made a little change. It seems to fix the links, but I’m not sure if there will be other side effects.

Test http://www.banggood.com/BLF-A6-CREE-XPL-3D-74modes-Flashlight-Nitecore-UM20-2x18650-p-998532.html

Quote myself.

Pretty picture:

Common boilerplate side effects from treatments include nausea, dry mouth, headache, dizziness. :GRADE:

:wink:

Nope, sorry. If I fix links with dashes in them I end up breaking other more important functions like posting images.

Simple URLs usually work still: New Arrivals for - The Greatest Discount on Top Quality Products at Banggood

The best way to post those long ugly URLs is by using link text like this.

why did it work before but not now?

It’s never worked correctly since the upgrade. I tried a way to fix the links, but it broke posting images.

In what way did the fix break images? It seems like automatically picking out images should be easy since the string starts with a “!” symbol.

i meant before the upgrade

It’s different code now after the upgrade, and there is an unfixed bug which will probably never get fixed.