To insert code use <code>...</code>.
Wordpress 3.1 compatibility - Prior Discussion Archived and closed with Ver 3.0 release
  • Hello there,

    Just tested striking with wordpress 3.1

    Everything works except the issue with ie. Learn from http://kaptinlin.com/support/discussion/905

    If anyone find anyother issues with wordpress 3.1 after upgrade, please let me know. Thanks.

    Regards,
    KaptinLin
  • 51 Comments sorted by
  • Hi there,

    For wordpress menu doesn't working issue, you can check your install of striking.

    Just need upload the folder striking to wordpress.

    Learn from http://wiki.envato.com/buying/support-buying/solving-broken-theme-issues/


    Regards,
    KaptinLin
  • Still having issues with the wordpress navigation not working.
  • Hi robertdonovan,

    Can you give me a permission to your wordpress admin panel?

    My email is kaptinlin@gmail.com

    Regards,
    KaptinLin
  • Hi KaptinLin, I am having the same issue as well with the navigation not working.

    When in the menu area, the main menu and footer menu is blank, but if you try to save a menu, it won't stick and will find it blank when you go back to it.
  • Hi KaptinLin, I am having problems with the lightbox on the portfolio page since updating to wp 3.1. I looked at some other striking sites and they have the same problem. When you click on the image instead of the larger image displaying, the screen just goes dark. Check out this page to see what I mean. http://kaptinlin.com/themes/striking/portfolios/sortable/portfolio-3-columns/.
  • Kaptinlin,

    Maybe this is why I cannot use the Custom CSS section. Nothing I place there has any effect on the website. I have changed all permissions and followed all instructions suggested for customizing the background of pages but the CSS section is unresponsive.

    The thing I don't understand is that everything worked fine at first and the css section was working. Then it stopped working for no reason. So I don't see how changing anything on the file permissions will help since it worked the way it was.

    Any help on this is appreciated.
  • Hi robertdonovan & derekz007,

    Just found a solution for navigation menu can't save issue with wordpress 3.1.
    You can change your theme to wordpress default theme Twenty Ten 1.2.
    Then switch back to striking.

    After doing that, go to 'Appearance'->'Menus' option page, the menu system will works.

    Regards,
    KaptinLin
  • Hi coolwave,
    image

    If so, you can edit on 'striking/custom.js' file.

    Locate line 100 & 154 & 184 & 203, change 0.7 to 0.5 or lower.

    Regards,
    KaptinLin
    1.jpg
    941 x 819 - 112K
  • So is Striking compatible now? Is the latest download available from themeforest??
  • Ian - not completely no, we're waiting on the update from Kaptin. I think the best course of action is to not update to 3.1 until then.
  • Hi ianforest,

    I still wait for more feedback about wordpress 3.1 compatibility.
    When no more issue happens, will give a notice about it.

    Regards,
    KaptinLin
  • I tried this but unfortunately it didn't solve the problem for me:
    ------------
    Hi robertdonovan & derekz007,
    Just found a solution for navigation menu can't save issue with wordpress 3.1.
    You can change your theme to wordpress default theme Twenty Ten 1.2.
    Then switch back to striking.
    After doing that, go to 'Appearance'->'Menus' option page, the menu system will works.
    Regards,
    KaptinLin
  • Just purchased your theme and am trying to set it up on 3.1. As above I am having the same issue with the WP menus and the Twenty Ten toggle isn't working for me. Also I am not getting the 3D slideshow to work, but am not 100% that I am setting it up properly. Seems pretty straight forward and the other slide shows are working so it may be a 3.1 issue.
  • Hello all,

    I have fixed my issues with the custom css. I now don't think that it was the WP3.1 upgrade. I think the source of the problem was the Striking 2.1 update. Everything else worked fine but the custom css section stopped working like it had before.

    I had to recopy all 2.1 Striking files back over to web server and I also changed permissions on the specified folders/files. Took 3 minutes at most. Not sure why it worked before. Maybe the permissions becomes more of an issues with 2.1 update. This seems to correlate with others who had the same problem around the time of a theme update.

    Thanks for an awesome theme and great support! Remember, you can always donate a few buck (or more) to Kaptinlin if he's been helping out with mods and customizations. Think about what this would cost you if you had to pay someone for the skills. I've never had a theme author be so thorough with his follow up support for things way beyond bug fixes (which there aren't many needed). Plus, I've learned a lot about coding and design here.
  • Regarding the navigation menu issue: Just tried the toggle fix, and couldn't get the menu to work with striking. I was able to get the manu to work with the Twenty Ten 1.2 theme, but when I switched the theme back to striking, still had the same issue. Any other ideas or fixes?
  • Also having the custom menu issue here. Toggle did not work and I tried the toggle with other themes as well. I am going to try turning off the front end admin menu (that 3.1 automatically puts on the end user site if you are logged into the admin...see if that helps.
  • Having the Navigation issue here as well. So far I have tried the toggle between Twenty Ten and the Striking theme, as well as overwriting my 3.1 installation with 3.05 (as mentioned by "Websys" in this thread = http://kaptinlin.com/support/discussion/comment/3165/#Comment_3165). Still my custom menu is not working at all. Very frustrating. Any other ideas for a fix????
  • Just to throw my 2 cents in... I've upgraded WP to 3.1, but I have not updated Striking beyond 1.9.1 - a simple oversight on my part. I am NOT having any of the reported compatibility issues.
    I don't think I'll be updating Striking until the 3.1 compatible version is released. :)
  • Hi NetBizCoach & derekz007 & likemike & likemike,

    Can you give me a permission to your wordpress admin panel?
    My email is kaptinlin@gmail.com

    Regards,
    KaptinLin
  • Hi wintensive,

    For custom css section stopped working, have you give the files with correct permissions?

    Thanks for your kind words.

    Regards,
    KaptinLin
  • Hi Kaptinlin,

    Some feedback for 3.1
    Seems like the new internal link function is not working with Homepage options editor. It works with page/post editor, but not with homepage options editor.
  • KaptinLin I tried reverting to the default theme and back and the menus are still not working. I've sent you an email about logging into my dashboard.
  • I am also having the same custom menu issue after upgrading to WP 3.1. I am running Striking 2.2.3. Ive tried switching back to twenty ten and saving it but it doesn't save when I go back to striking. Any ideas?
  • When can we expect a 3.1 compatible version, week? month?
  • Hi robertdonovan,

    You also need re-install striking.

    Learn from http://wiki.envato.com/buying/support-buying/solving-broken-theme-issues/

    Just need upload the folder striking to wordpress.

    Regards,
    KaptinLin
  • Hi dfwREguy,

    Can you give me a permission to your wordpress admin panel?

    My email is kaptinlin@gmail.com

    Regards,
    KaptinLin
  • Hi debban,

    I think the theme is already compatible with wp 3.1.

    Anyway, i will release a update asap.

    Regards,
    KaptinLin
  • Hi,
    I'm also having the same custom menu issue after upgrading to WP 3.1 and running Striking 2.2.3. Ive tried switching back to twenty ten and saving it but it doesn't save when I go back to striking. And I have also tried re-install striking with the same issue.

    Regards,

    Mikael
  • hello, same for me drop down menu not is working Your text to link...
    any suggestion
  • Hi Mikael,

    Can you give me a permission to your wordpress admin panel?

    My email is kaptinlin@gmail.com

    Regards,
    KaptinLin
  • Hi tripmaitrop

    You don't install striking correctly.

    See your source code below:

    image


    The theme is under '/wp-content/themes/striking-premium-corporate-portfolio-wp-theme/striking/' folder.

    The correct one is '/wp-content/themes/striking/'.

    You can learn from http://wiki.envato.com/buying/support-buying/solving-broken-theme-issues/

    Just need upload the folder 'striking' in the zip package to wordpress.


    Regards,
    KaptinLin
    1.png
    998 x 60 - 5K
  • That did the trick! the custom menu is working again! Thank you
  • Are you going to post the 3.1 version here before themeforest?
    Also are you adding features to the new version or is it just a fix for 3.1?
  • PM sent via email Kaptin, but menus are working - if that was you, then thankyou!
  • I'm having the same issue as coolwave. Since updating to wp 3.1. When you click on the image instead of the larger image displaying, the screen just goes dark. http://www.erdadesigns.com/art/

    I have followed your instructions on modifying the custom.js file but its not that the background goes dark. The issue is that when you click on the image it does not open up in the lightbox window.
  • Hi erdaestr,

    You may upgrade striking to the latest version first.

    Regards,
    Kaptinlin
  • Yes, I have the latest version no? 2.1?
  • Ok. Never mind. I now realized I did not have the latest version. This did fix the problem. Thanks so much. I'm sending two of my other friends to purchase your theme so I can help them build their sites too. Thanks sooooo much!!!
  • KaptinLin said:

    Hi debban,

    I think the theme is already compatible with wp 3.1.

    Anyway, i will release a update asap.

    Regards,
    KaptinLin




    Is there an update? Also are you adding features to the new version or is it just a fix for 3.1?



  • Hi debban,
    I will add some new features to the new version. And it will fully compatible with wp 3.1.

    Regards,
    KaptinLin
  • debban said:

    When can we expect a 3.1 compatible version, week? month?



  • KaptinLin said:

    Hi robertdonovan,

    You also need re-install striking.

    Learn from http://wiki.envato.com/buying/support-buying/solving-broken-theme-issues/

    Just need upload the folder striking to wordpress.

    Regards,
    KaptinLin




    Awesome KaptinLin, that did it. Thank you!

  • KaptinLin said:

    Hi tripmaitrop

    You don't install striking correctly.

    See your source code below:

    image


    The theme is under '/wp-content/themes/striking-premium-corporate-portfolio-wp-theme/striking/' folder.

    The correct one is '/wp-content/themes/striking/'.

    You can learn from http://wiki.envato.com/buying/support-buying/solving-broken-theme-issues/

    Just need upload the folder 'striking' in the zip package to wordpress.


    Regards,
    KaptinLin



    I have debugged.
    Apparently wordpress 3.05 installs striking theme under "striking" folder.
    Wordpress 3.1 installs it in striking-premium-corporate-portfolio-wp-theme/striking/ and so menu does not work.

    I simply renamed the folder striking-premium-corporate-portfolio-wp-theme to striking and now all works well.
  • Will the next version of Striking support WP 3.1 Post Formats?

    Best
    ~C
  • Hi everyone!

    See the last comment in the sticky on Closing Threads. The update is very close at hand, and our last comment in it clarifies better the timing.

    Kaptinlin is very hard at work. He was quite ill for the last few days, and only really getting back on his feet today. So please be patient. The draft testing of the update seems to be fully WP 3.1 compatible - BUT NOTE TO ALL, STRIKING IS A COMPLEX THEME AND MOST LIKELY SOMEONE IS GOING TO FIND SOMETHING EVEN WITH KAPTINLIN'S EXTRAORDINARY SKILLS. DON'T HAVE A HAIRY IF YOU DO!!

    Also we hope to have somewhat of a support forum reorg to coincide with the update, as it is transitioning to WP3.1 and we want to isolate new threads related to WP 3.1 bugs (if any) to a new common area.

    So when the update is released, we request all post any comments, questions or bugs related specifically to the release, in the new forum section. For example, if you are wanting to know about a css code to do something - that is not WP3.1 related, and would not be posted in the fortchoming WP3.1 thread.


    Happy Striking
    Websys Team on behalf of Kaptinlin.
  • hmmm, I'm still having issues with my navigation since updating to WP 3.1. The Navigation and the links in the slideshow have completely stopped working. My site has been rendered pretty much completely useless. The solutions provided in this thread haven't proved useful. I did email kaptinlin my site's login url and info, hopefully that will help. If anyone has any suggestions I'm open!

    http://www.seedsandroots.org
  • Hi Striking Users!

    Kaptinlin has been extremely sick since late last week, and of course this has put things a little behind on the next Striking update.

    While we do not understand why anyone is using Ver 2.2.3 with WP 3.1 when it is not certified compatible (are there not enough warnings. comments and threads at this point for everyone to get the point?), if you do not want to go back to WP3.0.5 (very easily done) and none of the suggestions have worked for you, your only recourse is to wait.

    The release has several exciting new features as well, and should continue to provide all the leading features and flexibility that everyone loves about Striking. And it is fully WP 3.1 compatible.

    Again, it would be unreasonable to expect that given all the installations of Striking on so many different hosts, it will be perfect for all WP 3.1 upgrades. It should be zero problems in 99% of all instances unless something occurs that he just did not see or missed. But testing on a live server to date has been fine. So keep your fingers crossed!

    The revised schedule for the release is for Kaptinlin to submit the update to Themeforest this Friday. If there are any further delays due to illness on Kaptinlin's part, we will advise the forum.

    Best Regards
    Websys Team on behalf Kaptinlin (who is in bed getting well this moment!).
  • Hi jamarwright ,

    That's wordperss permalink issue.

    Just help you fix it.

    Regards,
    KaptinLin
  • KatptinLin,

    Just in case in anyone else had the trouble with their navigation not working, KaptinLin instructed me to go into my permalink settings to resave the settings. This fixed all my navigation woes with Striking and WP 3.1. Hopefully this can help someone else! Take care!
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