Jump to content

Website Software Upgrade


Mark

Recommended Posts

Via tapatalk.....

When I go back and edit a post, I now get blank lines inserted between lines of text.

I believe this is a Tapatalk issue. The developers of Tapatalk have not yet allowed for the fact that IPB is not using BBCode any more and is storing the posts with HTML formatting. It is something a lot of Tapatalk users are complaining about.

We'll have to wait for Tapatalk to catch up.

Link to comment
Share on other sites

7 minutes ago, Mark said:

Strange one. I can't replicate the error. Quoting came up perfect. Tried several posts.

If you have non-posted content in the editing window, sometime hitting "quote" doesn't add, or replace it. But if you clear the content, it works fine. Something to do with CKedit handling temporay content.

The feature of partial quoting by selecting text then hitting the notification pop-up is nice.

Link to comment
Share on other sites

I have had no problems logging in to the site since the change but, tonight I kept getting an error message.

I have had to enable an exception in order to allow me to login and access the site. I am using Firefox, version 45.0.1. I don't think there have been any recent updates installed by Firefox on my pc.

It might be something or nothing, I just thought I would advise you on what happened tonight.

Here is the message that appeared.

www.watchrepairtalk.com uses an invalid security certificate. The certificate is not trusted because the issuer certificate is unknown. The server might not be sending the appropriate intermediate certificates. An additional root certificate may need to be imported. Error code: SEC_ERROR_UNKNOWN_ISSUER

Link to comment
Share on other sites

On 25/03/2016 at 8:46 AM, Spandrel said:

This method will disable all notofications for all sites, so be aware of that.

In the Firefox address bar type "about:config" without the parentheses then press "enter". You may be presented with a dire warning of the world ending or some such like. Press "OK I'll don full protective headgear" or whatever and press "enter".

In the search box type "dom.web" and find the line "dom.webnotifications.enabled". Double click on it and the "true" will turn to "false". Restart your browser and the nags have ceased.

Mark posted the above just before me and his solution seems the better option as it disables notifications only for this site.

Thanks again Mark.

I have had the same problem and I also use firefox.

Link to comment
Share on other sites

Nothing to do with the software upgrade.

I installed a new server SSL certificate last night - it's most likely related to that.

Works fine in my Chrome browser and also Safari.

Now I have to download Firefox to text :(

The things I do for you guys. Lol

:)

Link to comment
Share on other sites

OK Guys,

I think I have resolved this - I had the wrong intermediate certificate installed. I have replaced this and done some other tweaks.

I had a third party testing website check it out and the following browser/OS combinations show good results apart from IE6 and IE8 on WinXP. But this site won't work on those browsers anyway me thinks - they are too old.

 

Android 2.3.7   No SNI 2RSA 2048 (SHA256)  TLS 1.0TLS_RSA_WITH_RC4_128_SHA  No FS  RC4

Android 4.0.4RSA 2048 (SHA256)  TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp256r1  FS

Android 4.1.1RSA 2048 (SHA256)  TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp521r1  FS

Android 4.2.2RSA 2048 (SHA256)  TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp521r1  FS

Android 4.3RSA 2048 (SHA256)  TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp521r1  FS

Android 4.4.2RSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp521r1  FS

Android 5.0.0RSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp521r1  FS

Baidu Jan 2015RSA 2048 (SHA256)  TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp256r1  FS

BingPreview Jan 2015RSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp521r1  FS

Chrome 48 / OS X  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS

Firefox 31.3.0 ESR / Win 7RSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS

Firefox 42 / OS X  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS

Firefox 44 / OS X  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS

Googlebot Feb 2015RSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp521r1  FS

IE 6 / XP   No FS 1   No SNI 2Server closed connection

IE 7 / VistaRSA 2048 (SHA256)  TLS 1.0TLS_RSA_WITH_AES_128_CBC_SHA  No FS

IE 8 / XP   No FS 1   No SNI 2RSA 2048 (SHA256)  TLS 1.0TLS_RSA_WITH_RC4_128_SHA  RC4

IE 8-10 / Win 7  RRSA 2048 (SHA256)  TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp256r1  FS

IE 11 / Win 7  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS

IE 11 / Win 8.1  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS

IE 10 / Win Phone 8.0RSA 2048 (SHA256)  TLS 1.0TLS_RSA_WITH_AES_128_CBC_SHA  No FS

IE 11 / Win Phone 8.1  RRSA 2048 (SHA256)  TLS 1.2TLS_RSA_WITH_AES_128_CBC_SHA256  No FS

IE 11 / Win Phone 8.1 Update  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS

IE 11 / Win 10  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS

Edge 13 / Win 10  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS

Edge 13 / Win Phone 10  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS

Java 6u45   No SNI 2RSA 2048 (SHA256)  TLS 1.0TLS_RSA_WITH_RC4_128_SHA  No FS  RC4

Java 7u25RSA 2048 (SHA256)  TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS

Java 8u31RSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256   ECDH secp256r1  FS

OpenSSL 0.9.8yRSA 2048 (SHA256)  TLS 1.0TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 2048  FS

OpenSSL 1.0.1l  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp521r1  FS

OpenSSL 1.0.2e  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS

Safari 5.1.9 / OS X 10.6.8RSA 2048 (SHA256)  TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS

Safari 6 / iOS 6.0.1  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS

Safari 6.0.4 / OS X 10.8.4  RRSA 2048 (SHA256)  TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp256r1  FS

Safari 7 / iOS 7.1  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS

Safari 7 / OS X 10.9  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS

Safari 8 / iOS 8.4  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS

Safari 8 / OS X 10.10  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS

Safari 9 / iOS 9  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS

Safari 9 / OS X 10.11  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS

Apple ATS 9 / iOS 9  RRSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS

Yahoo Slurp Jan 2015RSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS

YandexBot Jan 2015RSA 2048 (SHA256)  TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp521r1  FS

Link to comment
Share on other sites

  • 2 weeks later...
The server now presents the mobile interface when accessing from my usual desktop. Why that could be?

This website is now responsive. That means it will present itself differently depending on the size of the window. If your browser window is below a certain size then it will present as a tablet or mobile website.

Maximise your browser window to full screen and refresh.

I'm going to close this thread as the software upgrade happened quite a while back :)

If you are still having problems please feel free to start a new thread or open a support ticket using the "support" link in the main menu above.

:)

  • Like 2
Link to comment
Share on other sites

  • Mark locked this topic
Guest
This topic is now closed to further replies.



  • Recently Browsing

    • No registered users viewing this page.
  • Topics

  • Posts

    • An update, for everyone who contributed advice, and for those who come after with a similar problem. Based on the answers received, I decided to work on the face of the hammer first. I used a square degussit stone to guarantee a vertical surface to work against, and ground the face back until it was square across 90% of the depth. I was conscious of the risk of removing too much material.* After I'd got the shape how I wanted it, I polished the surface with lapping film. To cut a long story short, it did the trick and the hammer hasn't slipped off the cam since. Of course, that wasn't the end of my problems. Have a look at this video and tell me what you think is wrong. https://youtu.be/sgAUMIPaw98 The first four attempts show (0 to 34 sec.) the chrono seconds hand jumping forwards, the next two attempts (35 to 47 sec.) seem "normal", then on the seventh attempt (48 to 54 sec.) the seconds hand jumps to 5 sec. and the minute counter jumps to 1. The rest of the video just shows repeats of these three variants. I solved it by rotating the minute counter finger on the chronograph (seconds) runner relative to the cam.  I'd be interested to hear your opinions on that. It seemed to be the right thing to do, but maybe I've introduced another problem I'm not aware of. * What is the correct relationship between the two hammers and cams, by the way? Should both hammers strike the cams exactly at the same time, or is it correct for the minute counter hammer to be a bit behind the seconds hammer? In this picture, I removed the adjusting screw at 1, and the hammers are contacting the cams simultaneously at 3 and 4. I had to turn the screw down tight to achieve this condition after stoning the seconds hammer and replacing the bridge.
    • It was easy enough to pop off. Once I had the cannon pinion hanging on the blades of the stump, I got my #2 tweezers on the gear attached to the staff and levered it down. That way none of the force was on the brass wheel itself.   I reinstalled it and the bridge, and it looks like a small but reasonable amount of end shake. It also spins easily with a blower. It stops quickly, but I think that's due to the large shoulder and about what I'd expect from this wheel.  
    • Oh, right. For some reason I was picturing a monocoque case in my head. Good looking watch!
    • Well said Ross. My reason for the thread, i like many of us dont want to lose the forum, such a well knitted group of individuals i feel. But things can happen out of anyone's control. Would be nice to have something in place just in case, if anyone has any ideas please speak up. 
    • Ok thanks Ross, I will give that a try!😁
×
×
  • Create New...