To insert code use <code>...</code>.
WordPress 3.4.1
  • Is it safe to update to WP 3.4.1 or its better to wait ?

    Have anyone tried ?
  • 24 Comments sorted by
  • Hi

    We are going to be testing and will, as always, update Striking asap. But until that time, we recommend users refrain from updating unless they have a local host or subdomain test bed which they can play around in - and we would gladly accept any test reports users have - just pm me with your experiences.

    Happy Striking
    Striking Team
    James
  • Sucks that I didn't see the message and I updated on our live site. No issues as far as what people sees but... When I change something in the admin section the site breaks. All my styles go away and I have to delete the cache folder and move what was in there back over via ftp.
  • HI Chayman

    Thanks for reporting. As I suggested to another user, ftp up wp 3.4 and write over your wp install, of course being careful not to accidentally mess around with your wp-config file.

    We are trying to work to an update on the weekend, but that is tentative.

    Best Regards
    Striking Team
    James
  • I am in the same position as chayman. Any instructions on uploading wp 3.4 via ftp? do I have to go to wordpress and download v3.4? Also, not sure what folder to upload it to. Do I upload to the wp-config? Thanks for your help.
    Bob
  • All my headings disappeared. Any h2 and h3 do not show at all.

    (Wish I'd read the warning here before updating.) Wordpress always seem so INSISTENT that you update right away.....
  • bfreer said:

    I am in the same position as chayman. Any instructions on uploading wp 3.4 via ftp? do I have to go to wordpress and download v3.4? Also, not sure what folder to upload it to. Do I upload to the wp-config? Thanks for your help.
    Bob



    Hi, If you go to the wordpress codex archive page found at

    http://wordpress.org/download/release-archive/

    you just download the Ver 3.4 zip to your local machine, unpack it, and then transfer it to your webhost by ftp.

    wp-config is a file, not the entire wp install. it is the file that contains the pertinent information to enable your wp installation to communicate with your host database, amongst other things.

    If this is all "greek" to you, send me a pm, with your host ftp and your wp admin logins, along with your skype id, and I will walk you through it. It literally only takes about 2 minutes.


    All my headings disappeared. Any h2 and h3 do not show at all.

    (Wish I'd read the warning here before updating.) Wordpress always seem so INSISTENT that you update right away.....



    I know, it catches up new users all the time. For over a year, we have always had a little blurb of one sort or another in our forum header warning users never to update wp until we have indicated to do such. Its very easy to revert back to the prior wp version, but still annoying. Every major update always plays havoc with premium theme users as we actually employ many core abilities that free themes do not, and so when these core abilities get amended for one reason or another, the functions hooking to them get broken. Thus our warnings never to update until we have checked Striking against the final release version.

    It would be wonderful if wp actually built into the admin a way to revert, but......

    Anyways, an ftp install of the prior wp version, which takes about 2 minutes, give or take, should fix matters.

    Happy Striking
    Striking Team
    James

  • I suppose I'm lucky. I updated to 3.4.1 with no issues at all, as far as I can see. Strange, isn't it?
  • Hi Stormy,

    I suppose I'm lucky. I updated to 3.4.1 with no issues at all, as far as I can see. Strange, isn't it?



    Some of the issues only occur when one tries to use a function in the back end, but the display of the existing content is fine. But there are so many variables from one site to the other - in any case if both existing display and using functions results in no errors for you, that is great!

    Happy Striking
    Striking Team
    James

  • Websys said:


    Some of the issues only occur when one tries to use a function in the back end, but the display of the existing content is fine.



    I'm using the backend extensively with no problems at all. In case I run into a bug, will it be fixed simply by reverting to 3.4?
  • Hi,

    Yes. Just revert. But it is equally important to hear about any errors.

    Happy Striking
    Striking Team
    James
  • Not sure if it's 3.4.1 related, but I've noticed it now. If you enable titleLinkable="true" in the portfolio, the title always links to the portfolio item itself.

    At least in the case of Link and Document items, it should link to the same page/URL that the image links to.
  • I updated to 3.41 before seeing this message, ugh! and think I am having a related problem. All of my links that are attached to images are opening a blank, looks to be an image lightbox rather than linking to the page url. Any thoughts?
  • For some reason your theme is applying lightbox logic to all images wrapped in an anchor. Please Advise this is very important!
  • Hi @imaginetek

    goto the striking general settings and set "Enable image link lightbox" to "off".

    Best regards,
    Striking Team
    Paul
  • Just adding so we dont forget

    Nivo slider caption don'show in slider in wp 3.4.1

  • Weird lightbox bug: a caption is not shown on the left column of a 2-column page, but if you move it to the right column, it works! This is using the image shortcode.
  • The weirdest bug now: http://www.stormymondays.com/

    In Safari (Mac) the font in the right column is slimmer (not smaller) than the left, and the line height is different. But the CSS is the same! I'm inspecting everything and can't find a difference!
  • Hi Striking Universe!

    We are busy testing Striking with the newest version of WP. What we are not finding is many issues at this time. A couple of small things to correct, but some of the errors being reported are not being found in our test beds.

    Of course we still desire to do more testing, and what would be helpful for us is if each of you reporting an error could undertake a slightly more rigorous verification procedure to determine if the error is Striking, or a plugin:

    1) please confirm that all your plugins are wp 3.4.1 compatible
    2) turn off your plugins temporarily
    3) test to see if the error is occurring with just Striking and WP running.

    IF it still is occurring, then please make a snapshot and attach it to your post in this thread, and also, please pm KaptinLin, Paul or I (and then add the others to the conversation) with your wp and ftp logins, as we will need to go check the errors ourselves. But we will only do this after confirmation that a plugin is not the issue.

    We would like to release an update Thursday or Friday this week. But we are unwilling to do such unless we feel we have done a reasonable job of addressing any potential wp compatibility matters.

    Happy Striking
    Striking Team
    James
  • @Websys & @Kaptinlin - thanks for your careful and professional updates. Best support, best theme!

    ~C
  • I have some major problems, actually - my IT staff upgraded to 3.4.1 despite my urging not to, and now the changes I make from the admin bar are not "sticking" to the site. My header (entirely HTML) is gone and won't stay, nor will the settings for the header height, logo bottom, etc. The content on "homepage" won't stay. Text/HTML in widgets disappears after a save.

    I can create pages and save them, but HTML in the more structural parts of the site is not working anywhere that I try to use it. It's as if the admin panel is not applying anymore...

    thanks for help.
    rhiannon
  • Hi Rhiannon

    I am wondering if the problem is Striking. We know from both following some threads and going into user setups since the release, and from other information on the web that a big issue with both wp 3.4 and 3.4.1 is plugins not being compatible and causing unusual behaviors (and with premium themes as well).

    I would recommend that as a first step, you updae to the latest version of Striking (currently 5.1.8.2 until TF approves .8.3) and then follow the steps of

    a) turn off all plugins
    b) go to the Striking Advanced panel and toggle the clear cache to on and save
    c) go to a Striking panel, such as the Color panel, and resave it to reset the skin
    d) go to your homepage and check it out. once on the page, do a hard refresh (flushing your temp local cache) and hopefully you are back on track

    I don't know if you have any advanced customization by way of js or php but hopefully the above steps get you back on track. I am also tempted to suggest that you reinstall Striking, and WP, but by ftp, just to confirm your installations. They each only take a couple of minutes by ftp, so I think worthwhile to do just to eliminate the possibility of a bad install.

    All of the above is in total less then 10 minutes work, and goes a long ways to eliminate the most usual culprits.

    If not its the usual drill, send us your web links plus your logins, and we will take a look. Striking works fine with WP 3.4.1 - in ver .8.2 there were a couple of very minor issues, but nothing of the kind that you are reporting. And we believe ver .8.3 should be compatible for everyone - nothing has turned up in our testing of the last week getting it up to speed for the release today.

    Please advise back.

    Happy Striking
    Striking Team
    James (on vacation but checking in to see what is happening in a spare moment....)
  • Thank you. Due to some oddities in the IT administrative structure where I am employing the theme, I cannot update it via WP - is there a way I can get the zip for 5.1.8.2 directly? I have my license code I can PM you or someone else.

    Prior to updating, the steps a-d above didn't help, but I'm hoping that will fix it after the update.

    thanks for your help!
    rhiannon
  • Hi Parvati

    As this thread is diverging, I am closing it. But I ask that you pm me should you have continuing issues.

    In the Striking Advance Panel, you can check for the update, and one of the options you have is to download the build. You can download the build which contains only the updated files, and you can still install it via the update button after you have downloaded the build. Or you can ftp into your site the updated files if this is what you would like to do.

    And of course, you have the option to completely inspect the update and see the code changes on a file by file basis.

    Happy Striking
    Striking Team
    James
  • Should any users find they have an issue related to this update, and they assess it is due to the Striking code rather then a plugin or other matter, please post in the Sticky thread for this release found under the All Discussions forum category.

    Thanks
    James
This discussion has been closed.
All Discussions

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion