bfarber

While we announced planned features for IP.Downloads 2.1 in October, we've been a bit quiet about it since then. This wasn't because we had forgotten about IP.Downloads, or because we had some secret thing going on in the background we didn't want to relay to you just yet. We simply wanted to take the time to test out the changes a little bit before applying them live to our site. We know everyone would be quite upset if the resources section was down for a prolonged period of time, so we knew we had to get it right. I'm pleased to inform you that we've now updated IP.Downloads here to version 2.1, and it seems to be running quite well. There's going to be bugs here and there, given that this is a pre-final release (please report all bugs you find to our bug tracker, as always), however on the whole we think you'll like what you see. So head on over to the resources section and take a look at the new and improved download manager. For those of you who contribute, you'll find a few nice features in this release which you might wish to take advantage of. While these are highlighted in the previous blog entry I linked to, a quick summary is as follows: You can now submit multiple files at one time per file record.You can now submit multiple screenshots per file recordWhen submitting links you can identify a link "type" (i.e. a mirror, for instance)Due to the improved file uploading process, a progress bar is now shown for all files uploading We look forward to your feedback! View full blog entry

Do you need technical support? You can obtain support via the client area, or you can try to obtain peer-to-peer support at IPS Resources.

No. ;) What happens is any tags that don't allow parsing within them are specifically looked for first and replaced with a macro. Then bbcodes are parsed in the order they're stored in the array, then the ones that don't allow parsing are put back in and the outer tags parsed.

That would work fine...assuming the media tag/img tag bbcode hasn't already been parsed.

Actually, this is only partially true. It's true that every bbcode is a custom tag, and is treated in the same manner. HOWEVER, custom bbcodes can execute plugin files, instead of run through the central routine, and in fact media tags are already run through a custom plugin file to parse (the /custom/defaults.php file in the bbcode directory). So it would be trivial to add additional processing to media tags specifically. It would not necessarily be easy to identify from within the parsing of a media tag, however, what other tags it is inside.

I have more to the patch that I'm testing on a site that was having issues. So far, so good. Apparently hasn't had any further problems all weekend. I hope to release an update later today. @AA - thanks. :)

No, iframes are not inherently dangerous. They're only dangerous if not used properly. 1) Requires a dangerous site to be embedded via iframe, which wouldn't happen (we don't put any arbitrary site into the iframe) 2) Hacker puts an iframe to a third part site on THEIR site - has nothing to do with our usage of iframes 3) We don't use any such CSS ;) 4) We don't use any such javascript ;) 5) We don't use any such css 6) We don't use any such redirection In all of those examples, they show how iframes can be misused. That doesn't mean they're bad to use, it simply means a hacker can use iframes for nefarious purposes. They can do the same with javascript, which we use extensively throughout IPB.

That's right, and would be here on this board too. In beta 2 the iframes were coded into the template, but in beta 3 javascript adds the iframes to that div when the page is drawn (depending on the type of communication the browser will make use of).

I have attempted to duplicate every bug reported to the tracker, and every bug I can duplicate I mark as such and fix. Bugs I can't duplicate I have STILL been working on and fixing (such as the online list issue I couldn't reproduce, but confirmed and managed to fix, and the CJOIN-0 error I've been working with customers on). I think it's kind of harsh to say we're "quick to assume" something when that's not the case. We start at the simplest explanation for a problem (such as chat not being installed properly) and work out from there to the more obscure possibilities. I think that's quite a reasonable process, as the simplest explanation is more often than not the correct one. The chat CSS file is nothing special. It's the same CSS file any application would add. There's no special code related to the chat CSS, and nothing in chat itself that would be able to cause alerts/issues like you are describing (that couldn't happen for any other application). @Colonel Wolfie- pretty sure I suggested earlier that it sounds like your skin templates and CSS weren't properly updated. You can rebuild them under the template tools section of the look and feel tab (click css and html under the third tool, click ip.chat, and run the tool, then use the first tool to rebuild all your skin caches). It's possible your CSS folder(s) aren't writable, and that might be why you don't have the CSS file.

The installation here is exactly the same as the one available in the client area. We have not customized the CSS or skin here for IP.Chat at all. What you see here should be what you see on your own forums (provided you have not customized the template, are using the default skin, etc.)

I'll say it again.... We're working on the CJOIN-0 error. I've been working with a couple of customers to log the error and why it's occuring, I've got some data to go on, and we will be working on it. Obviously you don't get it here. This is just one of a million things that happens when you release a beta to a wider audience. Different configurations and so forth cause things that you don't necessarily see in a controlled environment. As for the broken template, really don't know what to tell you. The only other possibility is that you don't have the new CSS definitions. If you had customized the chat CSS file, you need to revert that, and reapply your customizations to it again. We are running the exact same release you'll find in your client area. There is absolutely nothing different or customized to the codebase we have installed here.

For those with refresh, redirect, or display oddities - clear your browser cache. The javascript and skin stuff changed significantly in beta 3.

If you refresh do you have the same problem? Can you also PM me FTP access to your site please? I'll add some logging to help identify the cause of that error.

Beta 3 has just been released to your client area. You will need to upgrade to beta 3 before Chat will be functional for you again. Some important highlights of this update 1) IE7 support fixed 2) Opera support added 3) Clarification of error messages 4) Backend changes that should rectify some of the connectivity issues some of you have faced Note that you will need to run the full upgrade process. You cannot only upload the files as there are new language bits and skin changes that IPB needs to import.

That is NOT how the view new content worked in 2.3, however. So what you are asking for is NOT how 2.3 worked. In 2.3, view new content was 100% entirely based on your last_visit timestamp in the ibf_members table. We simply found all topics that were started after your last_visit timestamp (which is updated when you are not active on the site for at least 15 minutes). To replicate that, in your usercp, you choose for "View New Content Method" the option "Show me all new content since my last visit". HOWEVER, you said you want to see all content since you last marked as read. The closest option to that is "Show me all content that I have not read". This will find all content since you last marked as read that you have not actually viewed. For instance, if you mark the board as read, and 2 topics are posted, and you read 1 topic, only 1 would show on the view new content page.

This is a beta guys, remember to keep that in mind. CSTART-0: We have determined that this error means that you cannot make an outbound connection to our server. Usually enabling "allow_url_fopen" in php.ini (or use the .htaccess method suggested [url=") will resolve this issue. You may need to contact your host for assistance with this. CJOIN-0: I've done a little debugging and believe I've found the cause of this issue. I am working on an update that should hopefully address this issue, but we will require a little more testing first. You have been kicked from the chat room: I have found the cause of this issue and applied a patch to the chat server. You should no longer be getting this error message immediately upon launching the chat room.

That's not ban, that's kick. And I've just fixed the bug. I posted the query to fix the problem in the tracker already.

Colonel Wolfie that error means you have not yet installed chat. You need to go to Manage Applications and actually install the chat application. Uninstall the previous one, if you had it installed, and then click to Install the new one afterwards. As for the other error, if you are successfully using the spam service, it obviously means you can make outbound connections, so that possible problem is ruled out. As Charles said, we'll be investigating the various issues some of you have had to iron out the kinks. It's a beta, remember.

Please read the pinned topic in this forum. It explains how to obtain your account key.

It's likely the "You've been kicked" issue is due to a conflict with the maximum room count, and the fact that we are allowing unlimited use during the beta period. We are investigating this on our end and will update you shortly. @theGaVrA - I suspect your server is not allowing outbound remote connections, in which case you would be unable to use chat (or the spam monitoring service, for example). The "-0" in the error code means the chat script couldn't connect to our server.

And first round QA stages have already started.

Thanks for the positive feedback guys. :)