Strict Standards: Redefining already defined constructor for class BPDB in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.bpdb.php on line 183

Strict Standards: Declaration of BB_Walker_Blank::start_lvl() should be compatible with BB_Walker::start_lvl($output) in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bb-walker.php on line 148

Strict Standards: Declaration of BB_Walker_Blank::end_lvl() should be compatible with BB_Walker::end_lvl($output) in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bb-walker.php on line 148

Strict Standards: Declaration of BB_Walker_Blank::start_el() should be compatible with BB_Walker::start_el($output) in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bb-walker.php on line 148

Strict Standards: Declaration of BB_Walker_Blank::end_el() should be compatible with BB_Walker::end_el($output) in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bb-walker.php on line 148

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-object-cache.php on line 285

Strict Standards: Redefining already defined constructor for class WP_Http in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-http.php on line 67

Strict Standards: Redefining already defined constructor for class WP_Http_Cookie in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-http.php on line 1633

Strict Standards: Redefining already defined constructor for class WP_Users in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-users.php on line 11

Strict Standards: Redefining already defined constructor for class BP_Roles in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.bp-roles.php on line 11

Strict Standards: Redefining already defined constructor for class WP_Auth in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-auth.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-dependencies.php on line 33

Strict Standards: Redefining already defined constructor for class WP_Taxonomy in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-taxonomy.php on line 36

Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9

Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bp-options.php on line 26

Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9

Strict Standards: Non-static method BP_Options::prefix() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bp-options.php on line 49

Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9
<br/> <b>Strict Standards</b>: Non-static method BP_Options::get() should not be called statically in <b>/home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php</b> on line <b>9</b><br/> Problems posting/viewing responses « The Kurt Rosenwinkel Forum

Problems posting/viewing responses

(7 posts)

No tags yet.

  1. I was wondering if anyone else had problems viewing and posting responses.Maybe it's only me but I have not been able to view or respond to some of the posts I made recently...

    Register
  2. animitta
    Member

    Use Ctrl+F5, Luke!Maybe some bad caching problems with some browsers.

    All the Best
    Animitta

    Edit page
  3. aramaya
    Member

    I have had this problem too. If you renew the page while on it, it updates all the content.
    I was wondering if this was a site issue, or something to do with my browser (Safari).

  4. Ahhh...there we go...thank you!

    Admin
  5. docbop
    Member

    Safari and Chrome both have issues with the site because they both use Webkit as their browser engine.

  6. Mozilla also has issues...

  7. docbop
    Member

    could be ssl certificate issue, out of date or self generated.


Reply

You must log in to post.