Hans - Webmaster

Testing the image upload...

This is my setup at my office..

Testing the posting in the advanced text entry field, using the latest updated version of FireFox 13.0 to see if the issue has been resolved.

Nope, the issue is still there, but the standard text editor works fine.

Adding a reply using the advanced text option and testing for errors.

OS=Vista

OK, so FireFox 3.6.12 does not appear to display the same error on Vista as it does in other OS's. Very strange.

Posting with Safari on a MAC using the advanced editor.:confused::confused:

Safari works fine, so it must be something to do with the way Mozilla based browsers behave when posting data. Both Chrome and FireFox have common elements and are both Mozilla based.

The options, for those wanting NOT to get errors, are to change browsers to Opera, IE, or Safari. Now this may be a bit of an ask, but we are unable to find a fix for this, even in clean installs of browsers, where there are no plug-ins and is platform independent. That is to say the browsers that display this error do so, no matter what operating system it is installed on, be it MAC OSX, Win XP, 2000, Vista or 7.

We have been discussing an upgrade to VB 4 at some time in the future, however we are not certain if the social side will support the importing of the current application we use here.

Testing a post with FireFox on a MAC, using the advanced editor to check for duplicate header errors.

Yep, FireFox on a MAC also has the same issue.

Posting a response using the advanced editor using Opera, to see if the problem arises with this browser too.

Seems like Opera is fine, but FireFox and Chrome both return the duplicate post problem.

Some other users have reported that other browsers are also giving the same problem., I tried to post a reply here with Chrome and do see that the "Advanced" option also has the same issue.

I have been informed that some users have been recently experiencing posting issues in more browsers. This is a post - using Chrome - to see if I also have an issue.

Well, FireFox has just had an update, so maybe the problem has now been resolved.

Pity, still get the error when using the advanced mode, but not the "quick reply".

I had a look at the image names and we do state in a warning that there should not be any "#" in the file name, this does cause display errors in browsers. I renamed all the files and they now show up fine on the profile.

Hope this helps

Best wishes

Another post to this topic, to make sure that the notification does get through. I did test this in another topic and the notice came through fine, so everything should be back to normal again.

Again, apologies to all for any inconvenience, it has been rather frustrating from this end to resolve it, but all is well in the end.

Best wishes

Checking to see if the subscription mail is being sent

Hi guys,

Yes, this happened yesterday and it is as a result of many mail hosts getting very stickyt about the message header where the "from" address needs to be a valid mail account. This has been resolved and I did a test post and got the notification, so from today Jan 7, it should all be fine again.

Regards

I have no idea if it's related, but I can't post pics in my blog any more. The uploading process goes smoothly, and then the pics just won't show. I've tried it on firefox and safari.

I did test the posting on the HTN blog section using various browser and operating systems, but could not get an error to show. I managed to create new journal entries, edit existing ones without any errors showing at all. If you could check the version you are using and let me know what operating system and version you have, that would help me.

Also, if you could let me know what the file names are and what extentions of the images you are trying to upload, that would also help.

We are aware of this and it does seem to be a problem in vBulletin and certain browsers. It usually manifests when using the "Go Advanced" reply/post option and this is where there are all sorts of errors. When using the "Quick Reply" it works fine.

Hopefully we will have a fix for this as soon as possible.

Best wishes.

flyguy, is that a problem you are seeing here, or on the HairTransplantNetwork site?

Thanks Radius,

The error seems to happen only with Mozilla based browsers, such as FireFox and Google Chrome, as you also noticed, only when using the "Go Advanced" text option.

I am investigating this and as soon as there is a solution, it will be implemented.

Thanks.

Using the advanced option and Firefox to try and replicate the problem.

Yes, I do get an error with both Chrome and Firefox, but not with any other browser.

I am in the proccess of trying to establish what could be causing this and what can be done to remedy this issue.

This is another test to see if I can replicate the error. This time using Chrome and the advanced text editor.

I did get the error that was reported and then went back to the forum and the post appeared there.

Interestingly, when I edit the post and still use the advanced feature, as I did when I add the screen shot of the error, it worked fine, without any issues.

I only have seen this error in FireFox, when using the advanced text box. I also notice from the screen shot that some users have more than one tab open on the HRN. This could also be something worth noting. Does the error occure when only a single tab of the site is open, or is it in all cases.

These may be insignificant questions, but will certainly help to establish if the issue can be replicated for all users and then we can start to debug.

Thanks

Another test, this time using Ubuntu 9.1/FireFox and the advanced text editor, to see if I get the error.

Well, no error as yet, only on Win 7 and FireFox

:confused:

Using the advanced text editor and IE 9.

:cool:

Ok this seems to work fine with both the quick reply and the advanced. Only FireFox presents with the error.

Replying using the advanced text option does giv this error, but not the "quick reply". This is very odd as it only happens with FireFox and no other browser I have tested it with.

Replying using the advanced text option and have yet to see an error. This may just be one of those things that we can try and replicate and still not get the error as each user may have different browser versions and OS's.

Still not sure how to address this problem, if I cannot replicate it.

Replying using FireFox on MAC OSX and the "advanced" reply.