Wedge

Does it happen when you come back to a tab, or when you first load it?

In the past, I found that very rarely, when coming back to a tab (in Chrome), my div size math was returning a zero and I was stuck with zero-width divs in the user box. Sometimes I would also get much larger sizes than expected. I fixed that by being more careful about tab switching, but maybe Firefox doesn't play along.

Is the text out of bounds only when it's in follow_me mode, or even outside of it? (e.g. you're viewing the post before it.)

@TE, while I'm happy that the importer is smart enough to import from other systems, I think realistically we can assume that most Wedge users will be coming from a SMF background, at least until it gets popular enough to stand as an unmissable forum package.
For that reason, it might be best to go the extra length for SMF users.

Also, I thought that since the import script has access to the source's Settings.php, it could very easily re-use this file's user name & password when connecting to the source database..?

@Farjo, I think that what bothers Thorsten is the fact that these db user & password would be stored in a clear text file. However, it could just as well be stored in $_SESSION. I'm not exactly sure why it's a problem at all. The importer has little chance of compromising your website anyway.

I see...
Well, I have a potential fix for that, but I'm not sure it'll work. Stay tuned.

But that's only *there*, right..? Search isn't entirely broken to begin with?

Can you be more specific when you say something doesn't work...? Because it works perfectly for me now...

It was only broken due to a last-minute change long ago where I removed a test for the upcook query string, and replaced it for an AJAX test... Which was wrong on two levels: (1) I did the reverse of the test I was thinking about, (2) Flash-based uploads never use Ajax, they just use a regular request, so I had to actually force Ajax status in QueryString.php, which was a waste of time, (3) it also disrupted the template flow, and made it impossible to issue a proper response. Not my most glorious change in the codebase, indeed, but if there's one thing I can be proud of, it's that I don't have any problems recognizing my errors. In this case, it was a human error, and I'm happy it got a human solution. :P


Oooooh, new bug! Inline me's! Yay! :lol:

Just want to be sure of something...
Did you guys both enable proxy settings in Wedge..?

Admin > Server > Server (1st choice) > Proxy Settings.
I'm just asking.

Duplicate question....

Oh, the irony...

You must be using a very recent version of PHP. Recently they started deprecating mysql() functions.
It's an old importer script, and it was never converted to use mysqli(), unlike the rest of Wedge. Problem is the same on openimporter.
Either TE will fix it by tomorrow, or I'll look into it. In the meantime, you can always try to downgrade your PHP to 5.3, and retry importing.Ahum... Well, dunno how to fix these, I'm afraid.