You're right. Hmm. I'll look into it.
ETA: Can't find a manual override for the minutes. We may have to endure it until I get a chance to look more deeply into it.
Printable View
You're right. Hmm. I'll look into it.
ETA: Can't find a manual override for the minutes. We may have to endure it until I get a chance to look more deeply into it.
We might experience some sluggishness and glitches soon. I need to find ways to cut back on expenses and the dedicated server costs almost $300 per month; a shared server is much cheaper. The dedicated server is my biggest monthly expense next to rent! I'm not broke or anything, never fear, but I've realized recently I need to have more money saved for unexpected expenses (like hospital bills). All I can ask is that you stick with us even though the board performance will inevitably suffer.
ETA: Well, it turns out when you tell them you're going to cancel your service they all the sudden find ways to lower the price. I got it down to $100 a month and so I'm keeping it.
Wow, Soda I had no idea it was so expensive! Bless you for doing this. I'm so glad they gave you a reduced rate (the same thing happened with our cable bill when we were ready to give it up).
Wow, Soda! I had no idea it was so expensive either! I will try to send you some money to help out.
I'm glad they reduced the price for you! Sometimes all it takes is asking! :thumbsup:
Do we have any idea what is causing this problem?
The problem where you have one space between lines & it shows up
like this?
I'm tired of having to edit every post that has more than one line in it.
I'm looking into it but no luck so far.
Are you using Firefox Browser? It isn't happening to me in IE or on my phone, only when I use Firefox. It might be a problem with the latest browser update's compatibility with the WYSIWYG editor.
I did a Google search, and this came up:
https://www.fxsitecompat.com/en-CA/d...instead-of-br/
When I do a "view source" on this page, FP's posts are doing exactly this, adding a <br/> instead of a </div> at the end.
Ah! I see. That makes sense. It also explains similar problems I've encountered elsewhere.
So is the easiest fix just to download Firefox 60? I thought I had the latest update!
Did some further reading, and that's the main suggestion. A couple of people pointed out that vbulletin should issue some kind of go-between to work with pre- and post version 60, but I wouldn't hold my breath.