To insert code in a forum thread or comment wrap it in code tags: <code>...</code>.
RELEASED- STRIKING RELEASE VER 5.1.9.6 January 21, 2013
  • Striking Release Ver 5.1.9.6 - Jan 21, 2013



    NEW - JAN 24 - SEE ERROR COMMENT FOR THE DOWNLOAD TO OBTAIN TWO NEW WOO SETTINGS AND CORRECT A MINOR LANGUAGE ERROR IN A GENERAL PANEL SETTING


    We are pleased to release Striking Ver 5.1.9.6. This is a small maintenance release whose main purpose is to squash the few bugs that have been reported since the 5.1.9.5 version. Thankfully, the list is quite small, and mainly esoteric type errors. Through your reporting and our efforts and testing, we believe we have eliminated everything reported and we thank you for your co-operating on this matter. As of this moment of writing, we have submitted this version to Themeforest for approval. Once I have finished these posts, I will be activating the API and you will see the update notification appear in your dashboard.

    PLEASE NOTE THAT THERE IS A COMMENT BELOW FOR CHILD USERS, AND ALSO ANOTHER COMMENT BELOW ON CUFON USAGE IN STRIKING AND THE CHANGES AND LIMITATIONS OF CUFON IN THE THEME AT THIS TIME.

    To see the changelog, list of added, deleted and amended files, and code changes please go to the following link:

    http://api.kaptinlin.com/themes/striking/compare/from/5.1.9.5/to/5.1.9.6

    We have followed every error report and many of you will recognize fixes from your past reports:

    Version 5.1.9.6 - Jan.21th ‘13
    ===============================================
    Added : feature image option for single portfolio page
    Added : portfolio display as button attribute for shortcode
    Fixed : nivo slider caption opacity issue
    Fixed : kwick slider frame border issue
    Fixed : archive filter notice warning issue
    Fixed : search widget shortcode button text issue
    Fixed : custom post type feature text settings issue
    Fixed: Woo Commerce Custom Title in Archive pages
    Removed: editor-style.css files which were impacting the visual editor
    Updated : Anything slider js
    Updated : nivo slider js
    Updated : colorbox js
    Updated: Image sprite in main and child themes.
    Updated: Chilld Theme to Version 1.0
    Other: misc minor code tweaks


    We attempted to keep scripting changes to a minimum, and only updated scripts when there was a change that really demanded inclusion into the Striking core.

    We also are grateful for both all the error reports, and solutions, proposed by users. Those reports, and your patience, has improved Striking for the benefit of all the user base.

    Below this comment I will be posting separate comment for error reporting (which will also note outstanding issues), installation for normal users, and another for Child Theme users. Child theme users should read the child comment very carefully, as the process of updating any site when one has a child theme in place is neither as easy, or as quick as a default install, and requires more expertise. Should you be a child theme user and uncertain what to do, post in the forum.

    IE10
    We have done some testing and Striking is essentially IE 10 compatible. But! The installed base of IE 10 is negligible, and our opportunities to have a wider testing bed have been limited. Should you be an IE10 user and believe you are encountering some IE10 display matters, we ask that you please send a personal message to one of James or Paul, and include your wp and ftp admin logins. If you do not include your logins so we can test in detail, do not bother messaging at all - if we do not receive everything we need in order to test properly your message will be ignored, and most likely deleted. Incomplete reports and tools to correct have no value whatsoever. Help us to help you - be thorough and provide all the information necessary.

    PLEASE REVIEW THE FOLLOWING COMMENTS AS I POST THEM FOR INSTRUCTIONS ON REPORTING ERRORS, AND INSTALLATION FOR REGULAR AND CHILD THEME USERS


    Best Regards
    Striking Team
    James (on behalf of KaptinLin and Paul - aka BackuPs)

    Changelog.jpg
    918 x 638 - 122K
    New-Files.jpg
    772 x 344 - 57K
    Changed-Files.jpg
    1260 x 1486 - 102K
    DeletedFiles.jpg
    954 x 458 - 63K
    SuccessfullyUpdated.jpg
    1091 x 277 - 52K
    Installed successfully.jpg
    998 x 399 - 120K
  • 28 Comments sorted by
  • PROCEDURES FOR ERROR REPORTING



    ANY FUTURE FIXES THAT MIGHT BE NECESSARY WILL BE ATTACHED TO THIS COMMENT.

    All core errors, or what you suspect are core errors, are to be reported in this version thread, rather then on the open forum, other then any issues you may notice in respect of IE10 -> those please send either Websys or BackuPs a personal message.

    This concentrates the error reports in one place hopefully making it easier for everyone to track and discuss. Any code type errors reported on the forum will likely result in us asking you to cross post, and subsequent deletion of the external thread.

    If one finds a suspicious or non-conforming behavior, you should provide a url or a screenshot (a url is much preferable as it is the active scripting we really need to see in our developer tools), and if you feel it warranted, indicate in the comment that you have pm'd me (websys) with your wp and ftp admin level logins.

    We thank you to pay careful attention to the error posting guidelines as it really does make matters much more difficult to resolve quickly on your behalf when we are jumping back and forth. Insufficient information means no assistance and most likely your comment will be ignored, or possibly deleted.

    Known Issues or Reported Errors

    If you see an error you are experiencing already reported below, you do not need to report it again via another comment. Just follow for our resolution which will be posted below:

    -->> Youtube video - advances while playing - Carryover as not yet resolved. Use manual transitions with navigation enabled, or pause on hover, to help mitigate.

    Best Regards
    Striking Team
    James

    -------------------------------
    JAN 22 - The initial build of 5.1.9.6 had an error in a file,

    and the first 40 users who downloaded the build on the 21st before we became aware of the error have this error. I will be emailing each of you but should you have sorted portfolio on your site that stopped working, the file to install in order to correct is attached below "striking-portfolio-ajax-fix". If you are uncomfortable installing this file by ftp, please send me a personal message including your wp and ftp admins, and I will install it for you.

    Our apologies for the inconvenience.

    Best Regards
    Striking Team
    James

    ------------------------

    JAN 24 - UPDATE FOR WOO ARCHIVE SETTINGS.


    This is not really an error correction - although we have corrected the language of the title for the featured header site wide setting found in the Striking General panel, but rather this zip contains two new settings for manipulating the featured header and breadcrumbs on Woo Archive pages.

    The level of granular control we are providing here is somewhat absurd, but a user has asked for it, and we can see how some might view it applicable, so we added the abilities.

    All users are encouraged to install it by ftp as it also does contain some minor language changes to the featured heading and breadcrumb settings found in Striking General Panel/General Page Layout Settings.

    Best Regards
    Striking Team
    James

    -----------------------------------
    JAN 25 - GRAYSCALE ERROR IN PORTFOLIO LIST SHORTCODE


    We have confirmed that if one tries to apply a grayscale effect as part of a sorted portfolio list the scripting is behaving erratically in display of the portfolio items when one tries to go from tab to tab in the sorted items. So at this time we recommend one does not use the grayscale effect. We will provide an update for this in the near future to correct.

    Thank you to member dgoudy for reporting this bug.

    Best Regards
    Striking Team
    James
    --------------------------------------------
    JAN 27 - ADMIN ISSUES IN LATEST SAFARI BROWSER


    We have two reports of Striking admin settings not display correctly or not saving correctly when using Safari. While we investigate this we recommend a user stick to one of the other browsers when working in the admin.

    Thank you to members Fergofer00 & norskman for reporting this issue.

    Best Regards
    Striking Team
    James

    -------------------------
    Feb 5 - IE 8 DISPLAY ISSUES


    A user has reported some IE 8 display issues. We have yet to do all the appropriate confirmations but it appears some jquery handles are not being recognized in IE8. As we obtain more info we will update this comment.

    James

    -----------------------------
    Feb 5 - LEFT FLOAT BLOG IN 2+ COLUMN DISPLAY ERROR IN CHROME


    When one sets the blog panel settings for the default blog page to 2+ columns with the Featured Image Type setting of Left Float, the Chrome CSS interpreter is failing. For the time being, please choose an alternate Featured Image Type setting for your default blog page if you are using one unless Chrome visibility is not a factor in your site audience.

    Thank you to members JustProvence for reporting this issue.

    Best Regards
    Striking Team
    James

    ------------------------
    Feb 5 - RTL SETTING IN ANYTHING SLIDER NOT FUNCTIONING


    The setting for rtl in the anything slider is being ignored when set to On.

    Thank you to members YouLookgr8 for reporting this issue.

    -----------------------
    March 2 - ADDING CUSTOM FONTFACE FONT TO THE CHILD THEME


    It should be that if one adds a new custom fontface webkit to the child fontface directory, it should work for either selective replacement or replacement of all selective types. However although the font will show in the dropdown selector it will not work even when selected unless the webkit has been added to both the parent and child fontface folders. The filtering in our functions.php file in the Striking Child needs an adjustment.

    Thank you to members MandyMc for reporting this issue.
    ---------------------------------

    Best Regards
    Striking Team
    James

    striking-portfolio-ajax-fix.zip
    7K
    striking_woo_changes.zip
    30K
  • NEW STRIKING USER AND VER 5.1.9.6 IS YOUR FIRST EVER INSTALL:



    You would install Striking Ver 5.1.9.6 in the same manner as you would install any other wordpress theme. You can install Striking by using the install theme function in your wordpress admin, or by ftp into your host setup. The Document folder contained within your download from Themeforest has a section on installation of the Striking theme.

    Go to your Themeforest account and download the Themeforest Striking package. Unzip this package so you can access its contents. You will see several files and folders. One of these is "striking.zip". This is the zip file you will select when using the WP Install Theme function.

    It is a large package, so be advised that once you start the installation process, it may take up to 5 minutes for your site to upload and install it. Do not panic if it seems like it is taking a long time! If you go over 15-20 minutes, then you have a problem - in which case you can cancel and try again, or use ftp to install. If all else fails, post a comment and we will get in touch with you.



    COMMON INSTALLATION ISSUES:



    1) A very common mistake made by new users is that they try to upload the whole zip they have downloaded from themeforest. This results in an error message upon completion of a missing style sheet, or the install fails. Following are two video links:

    http://www.strikingsupport.com/Themeforest-Contents.avi
    http://www.strikingsupport.com/Installing-Striking-by-Wordpress.mp4

    Which were draft runthroughs made for a prior series of Striking. While a touch rough around the edges we believe they will help guide you on what you download from Themeforest, what you actually need to upload if using wordpress to install Striking, and how to install it using the Wordpress install theme functions.

    2) Another common installation issue is that the user receives some sort of theme installation failed due to it exceeding a certain memory size, or it just times out or goes on well past the 5 minute mark.

    In this instance, your host is likely a shared host (ie you have cheap web hosting) and there is a limit on the size of file you can upload using wordpress.

    Your options are to contact your host and ask or an increase in your php memory limit, or to install the theme by ftp.

    FALLBACK - INSTALLING STRIKING BY FTP:



    If for whatever reason the wp theme install function is not succeeding, one can always install Striking by use of an FTP program such as Cute FTP Pro, Filezilla, etc. This was the traditional way of installing WP themes and most other web software until early 2011, and is still the best method for certain types of situations.

    Following is a video I did in late 2010 or early 2011. The striking version is much different then, so do not try to compare folder contents and so on as they are much different. But the methodology for ftp transfer is unchanged. This video will walk you through the process:

    http://www.strikingsupport.com/Installing-Striking-FTP.mp4

    Any questions on installation, please put them in the regular forum, not in this thread for code and core errors.

    Happy Striking
    Striking Team
    James
  • EXISTING STRIKING USERS - YOUR CURRENT VERSION INSTALLED IS STRIKING VER 5.1.9.5 OR EARLIER


    For existing users, here is the process depending on if you use a regular Striking installation. The Child theme will be covered in a separate post.

    REGULAR USER - NO CHILD THEME IN USE:


    1. Go to the Striking Advanced panel and scroll down to the Update Theme section which is at the bottom of the panel.
    2. If you have not previously done so, enter your Themeforest purchase code into the "Item Purchase Code" field. The purchase code is found in a License Certificate document which you obtain from the "Download" section of your Themeforest account. I have attached an image of where you find the certificate. A few lines into that document you will see "Item Purchase Code" and it will be a long string of numbers, letters and dashes. IMPORTANT, DO NOT TRY TO INSTALL THE UPDATE YET. ONLY INPUT THE LICENSE CODE AND MOVE ON TO THE NEXT STEP
    3. Click on the "Save Changes" button after inputting your license code, your panel will refresh after saving and you will see yellow bar with the notification "page saved" appearing at the top of the panel.
    4. Now click on the "Update" button, and your theme should commence the update routine.
    5. Once the update is installed, go immediately to your Striking Advanced Panel, and in the General section go to the "Clear Cache" button and trigger it to "On" and save the panel. This clears the image temp cache folder. IF YOU FAIL TO PERFORM THIS STEP, MOST OF THE IMAGERY ON YOUR SITE SUCH AS SLIDER AND PORTFOLIO FEATURES IMAGES WILL CEASE WORKING!
    6. Now go to your homepage and other site pages and check to confirm that all your images and other media are working successfully.
    7. If you are still having a problem, see the section below "After Update I Have Site Issues"

    You should now be successfully updated Striking.

    INTERNAL UPDATE FUNCTION FAILED:


    There are times when your internal update attempt will fail. The two most common reasons are:

    - a plugin or other 3rd party js is interfering with the Striking update script
    - your host has security measures in place which prevent the site from communicating with our api

    Sometimes when the above happens, it will not be obvious at all why the internal update mechanism failed. It just will not work!

    Never fear. Should you not be able to update this way, then download the nightly build, or download the whole theme again from Themeforest, and install the build or the theme by FTP. The ftp instructions, including an instructional video, are found in the comment above NEW STRIKING USER AND VER 5.1.9.6 IS YOUR FIRST EVER INSTALL

    AFTER UPDATING I HAVE SOME SITE ISSUES


    If you find that for some reason, you cannot see your slider images, or your colors are not working, then we suggest:
    • you first go to your Striking Color panel and resave it, and if that does not work, then you may have to check your Cache folder permissions.
    • go to the STRIKING ADVANCED SETTINGS make sure you have set the following toggles:
      1. Turn Use Timthumb OFF
      2. Turn Clear Cache ON
      3. Turn Combine Css OFF
      4. Turn Combine js OFF
      Then save the Advanced Panel, and then check your site.
    • One might want to check one's .htaccess file - some users have added some custom code to their .htaccess file, and this has caused problems with updates. Try temporarily removing the .htaccess file and then resaving one of the panels or pages, plus clearing the cache, to see if that restores everything. If this works, then you will have to go through your .htaccess mods item by item to determine the problem.
    • Plugins: We think by now most users understand that on occasion a plugin can interfere with a theme function. So one of the very first measures a user should undertake after an update, should they find an issue in the use of the Striking theme is to deactivate all plugins and see if that makes a difference. Please note that generally, most security plugins and askimet do not conflict with themes, so you might not need to deactivate them, unless the security plugin rewrites the .htaccess file. If so, deactivate this only as a last resort. In this circumstance, it is ok to message us as per the instruction below, without deactivating, if you are uncertain or uncomfortable about turning off the security.


    If all else fails, then please post a message on the regular forum, as installation is not typically a code related matter but usage related.

    Happy Striking
    Striking Team
    James
  • CHILD THEME USERS - NEW CHILD THEME VER 1.0 UPDATE INSTRUCTIONS



    Child users have a completely different update process!! Please read carefully. This striking version has a new child theme due to a changes in several files including the functions.php file found in the Child. The new child version can be obtained by logging into your Themeforest account and downloading the Striking Theme - Striking Ver 5.1.9.6 has been approved by Themeforest.

    All child theme users have to:
    - deactivate the child switching to the Striking default.
    - save their custom coding they have in their child to their local machine.
    - remove the old child theme by deleting it.
    - update regular striking, which they can do within their theme dashboard or by ftp
    - upload the new child by ftp and redo your changes (which you have saved before) import those changes into the new child (which you could also have done local on your pc prior to the upload by ftp)
    - clear their cache for regular striking
    - activate the child, and clear cache again
    - confirm everything working.

    The above is the recommended way to update a child theme.

    Anyone who is unfamiliar with the child updating process may wish to contact us first.

    Prior to making any changes, unpack your theme forest download, and unpack the child zip, and confirm that you have version 1.0 y opening the style.css file. If you have a different version, or are missing it, send me a pm.

    We know we have many users who had sites professionally developed by a 3rd party, and a child was used, but they are unaware. So if in doubt, check with us first!

    Best Regards
    Striking Team
    James
  • CUFON USE IN STRIKING



    Cufon, as some user's may be aware, is becoming more and more problematic. No new themes support Cufon except in very rare instances -> and then on a very limited basis. On the Cufon homepage, the main cufon scripting file has not been updated in almost a year. We have resorted to writing our own cufon custom js due to the lack of updates.

    But this continued support is having increasing problems given the changes in java, browsers and the other ancillary components that together make a theme display. There was very serious debate internally on the Striking team about removing Cufon completely, as it now has reached some usability limitations. In the end it has been kept in Striking (for now) but effective immediately, the usage has changed and is much more limited:

    a) Only one cufon font can be active.
    b) no cufon replacement is possible - you either enable Cufon as the default font for all descriptive types, or turn off cufon completely
    c) do not try to use Cufon when you have either fonface or google fonts active.

    We did not want to take away the ability of one to use Cufon, although this is a very rapidly declining share of the user base. Most Cufon fonts are available in Fontface format, so we strongly recommend users switch to Fontface - it imposes a lighter js load on a page and does not conflict with any other scripts. Cufon scripting is also known to interfere with certain plugins.

    We regret the requirement to restrict the Cufon but the current state of Cufon makes it necessary in order for us to have it work successfully in Striking at this time. Extending the abilities of Cufon in Striking would take more time then we feel appropriate when the Cufon base is shrinking rapidly, and the demand for the forthcoming Striking Responsive release is growing exponentially. At a later date we may revisit the matter.

    Best Regards
    Striking Team
    James
  • Hello, thanks for the update, which worked fine on all installations but i found that the sortable portfolio doesnt work anymore:
    http://sound-und-design.eu/referenzen/
    http://www.synaesthetik.de/portfolio/

    thanks
  • Hi Everyone!

    Due to the report about the portfolio sorting not working I have temporarily turned off the update until we have a look at the code. I think it is just a little code error, but I am actually on the road, and so it will not be looked at for a few hours. Please check back in about 8 hours, and the update should be back on.

    Thank you TDS for the quick post. Very few users have installed thankfully.

    41 USERS HAVE UPDATED DURING THE PERIOD UP TO 5PM EST 21 JANUARY. If you are one of the users, please wait until you see the hold taken off the update function.

    I will post the fix to this comment, and you can install it by ftp. If you are unfamiliar with ftp, we will gladly install it for you. Just send us your ftp and wp logins and we will take care of the installation. I expect we will have the fixed files available in a few hours.

    Best Regards
    Striking Team
    James
  • Ajax matter has been fixed, and the api opened up again for downloads. The full build should be available for downloads from Themeforest in about 12 hours.

    I will post the Child instructions upon reaching my next destination.

    Best Regards
    Striking Team
    James
  • hi, how do i fix the ajax matter - as being already on 5.1.9.6 ...
    -------------------------
    Hi Augen.

    First, thank you for being "quick on your feet" and reporting the ajax matter as soon as you found it. It resulted in only a very few downloads with the incorrect portfolio ajax, and we are most grateful for your quick thinking in reporting.

    I am on a mobile phone right now. As I am traveling today. But later today I will post to the error comment the file you need to ftp in for replacement.

    Best Regards
    Striking Team
    James


    -------------------------------

    Augen, I have attached the file that needs to be substituted in your sites. The file is common.php found in striking/framework/functions.

    Please install it by ftp, and then confirm back to me that your portfolio ajax is resolved.

    Best Regards
    Striking Team
    James


    Ahh, thank you! It works now...
    striking-portfolio-ajax-fix.zip
    7K
  • Hi guys...

    Since the 5.1.9.5 update, my "play" button no longer appears on the audio player. I was hoping the latest update would fix it, but there appears to be no difference. I saw in the previous bug report section that this issue was believed to have been plugin related... I've deleted/disabled everything yet the problem persists. The site is http://www.wilsonvoice.com/

    Thanks!

    ---------------

    UPDATED: SOLVED.

    The issue has to do with the mediaelements plugin. From a support forum:

    "The control graphics are now being served as svg files instead of png files. There appears to be a fallback in the case that the browser does not support svgs.

    I had the same problem you are having. I suspect that you are not using svg images elsewhere on your site. You probably need to add some code to your htaccess file so that your server is sending the correct MIME type to your browser."

    SOLUTION: add the following to an htaccess file in the root directory of your WordPress install.

    AddType image/svg+xml svg

    -----

    Added that line to my htaccess and voila, we have controls again.

    Hope this helps anyone else struggling with the same issue.
  • Hi Guys,

    When is the instructions for Child Theme Users going to be done, i have the update notification in my dashboard but do not want to do it until i see the instructions. Thanks
    ----------------------------------------
    Hi my friend:

    I just posted them above. They are the same as for updating previous childs, I held back on posting them until we were sure TF had approved the full theme build, which they did earlier this evening. I was traveling until about 30 minutes ago, and only just got into a hotel and setup so I could undertake a few quick child posts. Although the child has changed slightly, the fixes in this release are not of the same urgency as the prior release - it is more maintenance oriented, and can be done by everyone at their leisure.

    Best Regards
    Striking Team
    James

    -------------------------
    Websys said:

    CUFON USE IN STRIKING



    Cufon, as some user's may be aware, is becoming more and more problematic. No new themes support Cufon except in very rare instances -> and then on a very limited basis. On the Cufon homepage, the main cufon scripting file has not been updated in almost a year. We have resorted to writing our own cufon custom js due to the lack of updates.......


    Cufon is dead and shitty method font replacement used a few years ago, the technology is now superceded with Google fonts, or Font face, it should be dropped in future versions period, it takes space and extra JS files that impeed on site performance. Just my 2cents for all who read.
    -----------------------

    Update worked out well.... thanks.


  • Websys said:

    CHILD THEME USERS - NEW CHILD THEME VER 1.0



    Child users have a completely different update process!! Please read carefully. This striking version has a new child theme due to a changes in several files including the functions.php file found in the Child. The new child version can be obtained by logging into your Themeforest account and downloading the Striking Theme - Striking Ver 5.1.9.6 has been approved by Themeforest.

    All child theme users have to:
    - deactivate the child switching to the Striking default.
    - save their custom coding they have in their child to their local machine.
    - remove the old child theme by deleting it.
    - update regular striking, which they can do within their theme dashboard or by ftp
    - upload the new child by ftp and redo your changes (which you have saved before) import those changes into the new child (which you could also have done local on your pc prior to the upload by ftp)
    - clear their cache for regular striking
    - activate the child, and clear cache again
    - confirm everything working.

    The above is the recommended way to update a child theme.

    Anyone who is unfamiliar with the child updating process may wish to contact us first.

    Prior to making any changes, unpack your theme forest download, and unpack the child zip, and confirm that you have version 1.0 y opening the style.css file. If you have a different version, or are missing it, send me a pm.

    We know we have many users who had sites professionally developed by a 3rd party, and a child was used, but they are unaware. So if in doubt, check with us first!

    Best Regards
    Striking Team
    James



    Hey James,

    Is it possible in a future version to have an internal check in place to see if the active theme is a child theme, and if so, to notify the user right where the Update info is, so it will be very clear to them if they are using a child theme, for those users you mentioned who had a theme created by a 3rd party?
  • Hi Folks - thanks for the update. What would be a similar replacement font for Segan, don't mind if it's a Fontface or a Google Font - thanks

    ------------------------------
    Hi:

    I am hoping someone on the forum might have some suggestions. I don't believe Segan exists at either fontface of Google fonts, although there is almost certainly something very similar. Regretfully, none of us internally know of something that is closely similar - its one of those tasks where you will have to peruse the font libraries to see if you can find something you think looks suitable for your needs.

    Best Regards
    Striking Team
    James
  • Can we update to WordPress 3.5.1? Thanks!

    ~C
    --------------------------
    Hi Colette:

    We are going to post shortly that from our perspective, based on our initial testing, Striking .9.6 and WP 3.5.1 are compatible. So I would say yes, go ahead and update. We have most of our test beds on it. We may have yet overlooked something but it seems that "in the main" we are good.

    Best Regards
    Striking Team
    James
  • i did update to 3.5.1 - without problems (but i read that this version still has some errors)

    Hi tds,

    where did you read what about what errors? btw i updates also to wp 3.5.1 without any problems (so far)

    Best regards,
    Striking Team
    Paul

    ----------------------
    hi Paul, the media upload has some errors and doesnt keep the tags, and some probs with the visual editor... (WP-Forum)
    --------------------
    27 Jan 2012 Hi All!
    Yes, there will soon be a WP 3.5.2 as WP has some minor bugs (as does pretty much all software on the planet). The codex has tracking for the list of outstanding issues.

    Regards
    James
  • I found a bug. Within the editor of a post / Shortcode Insert / Blog: the panel is incomplete, can not be used, fill missing fields...

    Striking 5.1.9.6+WP 3.5.1. Tested on OS X (Safari, Chrome, and Firefox).

    Thanks
    -------------------------------

    Hi @Fergofer00,

    I just tested under Win7, WinXP and Ubuntu. Can't see the bug you describe. Probably something exclusive to OS X. Can you post a screenshot?

    BR,
    Cris

    ------------------------------
    27 Jan 2013 Hi
    I think we have a report on the forum from another user that they were experiencing some admin issues with the latest version of Safari. I will go trolling for it shortly. It is one of the posts from the last 24 hrs. I do recall the user indicating they switched to chrome, and everything was fine.

    Thanks Ferg for including all the relevant details on what you were using, it helps greatly, but then you are a longstanding user and know the drill by now!

    We will check this out and advise above in the error comment where we track open issues.

    Best Regards
    Striking Team
    James
  • Hello,
    after updating the newest files i have an issue on all installations:
    After clearing the striking cache i get a black page.

    have a nice day

    Hi Tds,

    did you pay for each license? You are blacklisted? Fan of the Rolling Stones? :))

    Do you have a live link so we can see the problem? If you need any help on this can you grant me access to the admin part of your website? Just send me a private email with the login details to the admin. Click on my name and then on the left you can send me a private email.

    Please also include a link to this thread so i know what the personal mail is about.

    Best regards,
    Striking Team
    Paul

    27 Jan 2013 Hi Augen
    I to am quite curious about this although I my first puzzle is
    ""after updating the newest files""
    ->do you mean Striking 5.1.9.6 or the Woo zip? In either case, there are no problems of which I am aware - the Woo update was tested externally as well, so I am thinking that the issue is probably something simple to your setup - perhaps even a file was put into the wrong directory when you updated, or something else.

    I would appreciate being advised on this as soon as conveniently possible.

    Thanks
    James


    Hehe, sorry guys, a little typo error:
    i get no BLACK screen, but a BLANK screen when i empty the striking cache.
    i updated with the 2 files portfolio fix and woo changes in the post above...
  • Hi Sorry been a while since I have been doing internet stuff so very rusty. But I have updated www.gsdecorating.com to the latest versions both WP and striking, I did clear the cache as described in the update instructions. However my portfolios and sliders are now not workings. I have played about and tried searching the forums but to be honest I cant work out what to do.

    I couldnt find any link in the forum, sorry if you have already talked through this matter, but could you point me in the right direction of what to do please?


    Hi Greg

    i just visted your website and everything looks ok. Pls advice.

    Image and video hosting by TinyPic

    Best regards,
    Striking Team
    Paul


    Thanks

    Greg
  • Here I post a screenshot with the problem I wrote before.
    Thanks
    -------------------
    Hi

    Can you advise the version of Safari you are using? So we can check out in that version. Thanks
    James
    foto01.jpg
    1360 x 2006 - 210K
  • Here I post a screenshot with the problem I wrote before.
    Thanks
    -------------------

    Hi

    Can you advise the version of Safari you are using? So we can check out in that version. Thanks
    James

    It happens in all browsers:
    Safari 6.0.2 (8536.26.17); Chrome 24.0.1312.57; Firefox 18.0.1.

    -------------------
    Hi

    Ok, in order for me to make any further progress on this matter I will need your wp and ftp admins. Then we can do the appropriate testing to determine the nature of the error, as it seems to be unique to one or two cases, which implies that it is related to an external event such as a non-compatible plugin or a hosting setting, although this is to be determined.

    Best Regards
    Striking Team
    James
  • Minor issue with child themes & @font-face. Not sure if this is a bug or new, intended behavior.

    I was using Striking 5.1.8 and a child theme based on the 0.7.0 template. I updated Striking & the child theme following the given instructions but my @font-face wasn't showing (I'm using Colaborate Thin Regular & Colaborate Light Regular).

    It turns out with the update the fonts need to be in the child's fontfaces directory whereas previously they were in the parents'. The easiest workaround I found was to simply copy the desired font from the parent into the child.
  • Hi I eventually managed to get round to updating to 5.1.9.6 and all is well this time except that my twitter widget (again) is not working. any idea why this is happening? , its obviously something small again - I updated the theme about a week ago and left it thinking that it may just magically appear sometime, but a week or so later and still nothing.
  • Then another thing I wanted to queries. Reference is made to the authours in various widgets. It seems that the only time that a user's name will appear, is if in fact the user has been assigned the role as an author. If there is only 1 user - the administrator who will also be super admin in multisite - idealy that 'Admin's' name should appear in the author list.

    On my local machine with wp debug set to true - when I add the Authors Widget - I get the following error

    Notice: Undefined variable: all_authors in C:\wamp\www\mydomain.com\wp-content\themes\striking\framework\widgets\authors.php on line 25

    In the striking/framework/widgets/authors.php file - the following reference to this js file is made

    function add_admin_script(){
    wp_enqueue_script( 'authors-widget', THEME_ADMIN_ASSETS_URI . '/js/authors-widget.js', array('jquery'));
    }

    yet ... in the striking/js - there is no 'authors-widget.js' file

    Pse advise on this as there is def a problem here.




    hi

    i think you are looking in the wrong folder.

    THEME_ADMIN_ASSETS_URI is pointing to \striking\framework\admin\assets\

    so the script can be found in

    \striking\framework\admin\assets\js\authors-widget.js


    Best regards,
    Striking Team
    Paul
  • Ok I've found the authors-widget.js file - in the admin/assets/js folder
  • I think it's a bug, the shortcode generator doesn't works in full screen mode.



    Hi Shreejee,

    can you pls be more precise about what the problem is and what you mean by this?

    thank you

    Best regards,
    Striking Team
    Paul


    Hello

    I was talking about the WYSIWYG editor. Whenever I click on the fullscreen mode, the Striking Shortcode generator button present on the sticky menu will not work. Whenever I click on it nothing happens. No further menu, nothing.
    I really don't know if it's a local or a global issue. At least it doesn't works in my case.

    Cordially
  • Minor issue with child themes & @font-face. Not sure if this is a bug or new, intended behavior.

    I was using Striking 5.1.8 and a child theme based on the 0.7.0 template. I updated Striking & the child theme following the given instructions but my @font-face wasn't showing (I'm using Colaborate Thin Regular & Colaborate Light Regular).

    It turns out with the update the fonts need to be in the child's fontfaces directory whereas previously they were in the parents'. The easiest workaround I found was to simply copy the desired font from the parent into the child.



    Yeah this had us scratching our heads for a day or two also. I was like WTF? :) I messaged James about this, so I am glad I am not the only one who was doing that. It makes sense to support both options, so if a user wishes to put the fonts in a parent folder so it's accessible to all the children themes, then that is great. But should a user for any reason wish to limit access to the custom font, they just put it in the child folder.

    The strange thing about the current bug, is the font will show up as an option when placed in the parent folder, but it just won't attempt to load from there on the front end, it only looks in the child folder.
  • Another little bugger that I noticed, is the name of the Striking Menu for a child theme inside the WP dashboard. It used to be based on the child theme slug, but now even though i reviewed the code it appears to still be in place to do so, for some reason the variable gets reset, and it pulls the name of the parent theme slug for the 'Striking' menu name.
  • NOTICE TO ALL:



    We will be following with a final update of Striking Non-Responsive - Ver 5.2, in about a weeks time, perhaps less. It will coincide with its deprecation in favour of Striking Responsive.

    But Striking 5.2 will be supported indefinitely by updates available via the api only after it is deprecated. It will be supported for all future wp updates, and browser changes, until we see in the api that no one is downloading the updates.

    In the interim, as we have we believe a good handle on the little bugs in the current version, I am closing this thread. If one finds something new, that is not on the above list (which I will update fully in the error comment on Friday/Saturday), then please post on the forum.

    Best Regards
    Striking Team
    James
This discussion has been closed.
All Discussions