Forum Replies Created

Viewing 15 replies - 76 through 90 (of 121 total)
  • I got the briliant idea to NOT check on a superfat install and found something interesting. Tabs DO work with this in file-perm.js

    jQuery(document).ready(function () {
    	   jQuery("ul.tabs").tabs("div.panes > div");
    });

    They do NOT work with what I posted before. Not for me… They look as if they work but they are dead. JS never kicks in.

    Back to fat install with new tab init code but nope, they freaking still do not work. Tried forcing file-perm.js in footer, same result. There are no erors so I have no clue. Conflict I asssume.

    So try a bit of both 🙂 May be dev. should use jQuery UI instead if he/she can reproduce the working/not working states. Could very well be a conflict on my end though.

    Aaand it was. CSS from Post Snippets http://wordpress.org/extend/plugins/post-snippets/ kill the fun. A little too generic naming scheme for a file that apparently must be loaded on all pages! – or is it that this plugin believe there is no reason to be specific, it is not, as it only loads on 1 page! Dont know 🙂

    There are some things wrong with this plugin but easy to fix.

    1. Path to plugin folders is wrong in file-perm-check.php
    2. The version jQuery tools that is called is outdated and loads jQuery main file itself = WP do not like = JS errors
    3. Actually there are more JS errors as the init file file-perm.js is wrong. You just do not see tabs, your screenshot wpmu.org show how tables are one long string.
    4. When you have fixed those errors you see empty screen. Turns out there is a display: none for those tabs. That is why it works out of the box because CSS file is not even loaded due to wrong path.

    Fix 1 and 2:
    I commented out first chunk in file-perm-check.php, then changed next one to use correct file from jQuery tools and to use correct paths.

    //register jquery tools and tab styles
    /*
    add_action('admin_init', 'load_custom_perm_scripts_lcp');
    function load_custom_perm_scripts_lcp() {
    	 wp_register_script('my-jquery-ui', 'http://cdn.jquerytools.org/1.2.5/jquery.tools.min.js');
    	 wp_register_script('my-perm-js', WP_PLUGIN_URL . '/file-permission-check/file-perm.js');
    	 wp_register_style('jquery-style', WP_PLUGIN_URL . '/file-permission-check/file-perm-check.css');
             }
    */
    
    //load stuff only on plugin page
    //add_action( 'admin_print_styles',  'load_admin_perm_styles' );
    add_action( 'admin_init',  'load_admin_perm_styles_lap' );
    function load_admin_perm_styles_lap(){
    	if( (is_admin() ) && (isset($_GET['page']) == "perm_check") ) {
    		wp_enqueue_style('jquery-style', WP_PLUGIN_URL . '/wp-file-permission-check/file-perm-check.css'); // path to plugin is not file-permission-check
    		wp_enqueue_script('my-jquery-ui', 'http://cdn.jquerytools.org/1.2.7/tiny/jquery.tools.min.js', array('jquery')); // Does not load jQuery, only tabs
    		wp_enqueue_script('my-perm-js', WP_PLUGIN_URL . '/wp-file-permission-check/file-perm.js'); // path to plugin is not file-permission-check
    	}
    }

    Fix 3:
    Change content of file-perm.js to this

    (function($) {
    	   $('ul.tabs').tabs('div.panes > div');
               });
    (jQuery);

    Fix 4:
    Comment out or delete in file-perm-check-css

    /* tab pane */
    .panes div{
    /*	display:none; */
    	border:1px solid #666;
    	border-width:0 1px 1px 1px;
    	min-height:150px;
    /*	padding:15px 20px; */
    	background-color:#ddd;
    }

    And plugin seem to be fully working.

    Edit: actually it is not because there are still some tab issues. You can look up correct syntax at jquery tools site, http://jquerytools.org/demos/tabs/index.html then fix in plugin. Not so sure it is a CSS issue. Could be a HTML bug.

    Neat little plugin so would be cool if dev. did real fixes.

    I just had a fantastic idea! How about you made your position clear on entry of plugin? I realize this is being user friendly way over what can be expected, plugins typically just die, but wont you also benefit from this bold move?

    -10 points if you dont.
    +10 points if you do.

    Could also state plugin would be thankful for a takeover.

    And remove your email address 😉

    Thread Starter tzdk

    (@tzdk)

    Works, thanks!

    If your name keep popping up with these matters it will end up in google auto search. “Crap, theme dont” -> japh

    Highly messy thread though but Arconix Shortcode Collection is so superb it can handle even this 🙂

    Yeah it is great. But how many devs. you think need help avoiding newbie mistakes with CSS? Not even a programming language! None wil admit they do but I let CSS Lint be the judge 🙂

    Anyway, I hate half baked statements on the internet and now I just did it myself. So even if 200% off-topic here is some more info on this trickery:

    I dont know if it is correct or not. Do not care, it works. I have no access to perhaps more advanced editors doing this natively so have to fiddle. Also I imagine CSS-Lint god and godess are tough to beat with this so… Sublime text I believe have a plugin offering CSS lint but I use Notepad++

    Install node.js – I use 64bit version http://nodejs.org/
    Install CSS lint – check their site https://github.com/stubbornella/csslint/wiki/Command-line-interface
    Install nppExec plugin for notepad++ – done via plugin manager.

    Set up an “execute” in nppExec

    cd c:\program files\nodejs
    csslint.cmd --errors=compatible-vendor-prefixes --format=compact $(FULL_CURRENT_PATH)

    Set it up in menu via npp-execs adv. options. Perhaps assign shortcut via Notepad++ shortcut mapper.

    Show console dialog must be checked to see output form this command line script. Will pop up automatically.

    On their github wiki they show code for each check. I only use vendor prefixes as lack of those is also a generic error. However they have own ultra conservative idea of what “should” be there. Can follow their strict suggestions or not. Point is this also show lacking prefeix that really should be there. But main idea is superfast check for “newbie” syntax errors resulting in parsing errors. If not asked to check for anything it will only show parsing errors. More adv. people will probably want to add more. Really important to know where they are coming from, why they HATE IDs for example. If a slave to their ways good luck with any WP theme. Does not take away benefits and one is supposed to know what to check for.

    How to get file from internet in to Notepad++ with ease:

    I use this https://addons.mozilla.org/en-US/firefox/addon/jsview/?src=search drop down showing all CSS and JS files, in tool bar, in right click menu, in status bar. Chrome probably have something similar. So possible to check X file with few clicks.

    What if there is no file, just a code snippet? One that is selected in Notepad++. Use this which saves selection to temp file, then run CSS lint on it.

    set TEMP_FILE = $(SYS.TEMP)\npp_sel.css
    SEL_SAVETO $(TEMP_FILE) :a
    cd c:\program files\nodejs
    csslint.cmd --errors=compatible-vendor-prefixes "$(TEMP_FILE)"

    Yes, site fully working is first priority. I am sold on this tab script though 🙂 He does not do much advertising for the options of own CSS and even JS files. Dev. with thinking hat on. Nice!

    If japh reads this he might want to check CSS Lint http://csslint.net/ They are anal and have own CSS theory and policy. ALL WP stuff will fail and why you can tick things on/off – they know…

    Will hurt your feelings*
    (And help you code better)

    But if you go to their github you can see how to run Lint via node.js. Then Notepad++ (or similar), a little script setting it up to only check for newbie errors (evil must not exist parsing errors, even for free themes!), a little browser extension sending off CSS file directly in to editor. See? Amazing how fast and much one can check. May be reviewers are overwhelmed with all those lines and need help? These errors are typically 1 character and just lazy errors really. Someone needs to pick them up. Even some of your top dev. fail with this, I will bet 10 free themes from .org site it will take you minutes to go REALLY??? 😉 As with the script stuff this is also very very easy to avoid. Low hanging fruit might be what ThemeForest should focus on first? All connected me thinks. If you make it known to devs. silly errors means delay, potential rejection they will shape up. At least regarding CSS. A start.

    I am trying to be sarcastic but also wont thrash no. 1 without reason. So I had to add that…

    If I wrote what I really think should be done employees, “reviewers”, devs. connected with TF I fear moderation would kick in. japh is also ever so pleasant, doing what he is paid for naturally 🙂 I know it sucks for you and now you are all concerned about script age, know dev. probably could not care less, you might end up spending much TIME to fix this. Devs are only concerned about their time.

    You could do what I believe most will. Say good bye to Arconix and look for other tab script. Easy solutions are always welcomed. Get something up but then also be on the look out for better theme with more active and code aware developer.

    TF could copycat the term “Deprecated” from WordPress. Slap that on not updated themes. You could still buy them but have been warned. One day they might not work.

    Ok. Well odds are not good when a dev. have no problems selling outdated code + hints he is fully aware of the blame game.

    After further digging, like finding customers using that no. 1 theme I am not sure it actually mess up. I think it used to. Their demo site force 1.4.2 from own theme folder but the 2 sites I found load it correctly. I wonder if I have witnessed a miracle, a TF dev. bothering to fix old mistakes. If he can so can the rest = there is hope!

    Yes it would be a good idea. Unless you regard TF themes closed products not seeking incompatibilities (being LAZY!) is required. I do not understand why it is so difficult.

    Alternative is to declare that extra “3rd. party” code is not supported. You are on your own. Could be a new section in right sidebar, Yes or no. I could go with that, How most use a TF theme anyway I think. Just make it known to buyers and other devs.

    No. 1 selling theme seems to force jQuery 1.4.2 btw. http://dreamthemedesign.com/themes/u-design/

    So this power elite author with sales >1000000$ has fixed this little issue or you have not gotten around to it yet? Just curious on what “not acceptable” means in TF world.

    If there is room for more messages then perhaps an idea to send out one saying that all themes not compatible with latest WordPress will be removed, like 1 month from now. Will come as a shock so must be fair, to developers… And of course same faith will fall upon those with newbie mistakes like forcing load of year old jQuery. Seems like unnecessary problems that can be fixed easily. Just like last year.

    1. Have no clue as he could load it directly from some functions.php file or it could be in any file, like header.php. If not used to messing with these things I dont know what to say. Can you do a full text search or something from hosts control panel?

    <script type='text/javascript' src='http://www.fokkio.nl/wp-content/themes/Soon/js/jquery.js?ver=2.3'></script>

    is the line so “jquery.js” would be a good keyword. I do not know theme but as said look for functions.php, index.php, header.php or something like that.

    Right person to help is theme dev. and good luck with that.

    2. Good question 🙂 Because you asked that I think you can deal with no. 1 question. I think there is a good chance it will but of course he have more jQuery code programmed with 1.3.2 in mind. jQuery should be backwards compatible but dont know. Also there is a bunch of other scripts forced to load from theme so they are probably also quite old and might or might not have issues with newer jQuery. Just as newer script you add via plugins might not work with 1.3.2 – issues go both ways.

    Really a mess. Only reason I posted was because of interest for Arconix stuff. IF he had JS issues I would run away so had to check your site. Most likely a theme issue.

    But

    The tabs are not working anymore.

    mean they used to work, before you did what? or before what ever updated? Theme is still crap but there could be other issue… Fun. May be you should start with what John Gardner said, exclude plugins one by one. Should magic happen do not forget theme issues. I think you simply need to find a new theme as he have had 1.5 year to update and fix this. So start looking for an alternative theme regardless tabs start working.

    Good thing is nearly any new Themeforest theme will have tabs build in, well not good for Arconix but it is good for a TF theme as then less reason to add code to it 😉 Your theme dev. is one of their top seller so do not go by numbers. Lesser known can be better. I have never bought anything from TF but if I had to I would look for updates, change log, technical issues in comments. And even more for older products. I would also check source of demo. Actually I would even check CSS, all of it. If newbie/lazy errors in CSS what about JS and PHP? Would ignore looks and such 100%. Should be able to tell if X dev. is just freelancer no. 839 jumping on WP train or actually do know WP. There are good devs. on TF so not hopeless task.

    I find it just adds horror but to be fair to your theme dev. http://themeforest.net/item/soon-powerful-elegant-for-portfolio-business/147430?sso?WT.ac=portfolio_item&WT.seg_1=portfolio_item&WT.z_author=peerapong he actually only support WP up to version 3.1 Even then jQuery 1.3.2 was old but still. That is ThemeForest, and an “elite author” for you. I doubt there are technical reasons theme could not be WP 3.4 compatibility, he just has focus else where, sell more else where. And while doing that he keep selling this outdated stuff and TF lets him as when all gets money all are happy. Worst that could happen is grumpy users buy a new theme, probably on ThemeForest, and so it goes round and round 🙂

    From what I can figure out jquerytools used by this plugin is mainly tested and approved to work with latest or later jQuery versions. Your theme force jQuery 1.3.2 – on top of jQuery 1.7.2 from WP install. Typical horror theme from Themeforest. If you check devs. comment thread one of the last posts is him saying he really cant support all “3rd party” plugins. He has not updated this theme since for ever.

    Well, might or might not be important. If so it can be fixed but probably not by theme dev.

    Thread Starter tzdk

    (@tzdk)

    WP inline-edit you can get from here http://wordpress.org/extend/plugins/wp-inline-edit/ not some outsider you have to sign up for 🙂

    Try that with yours. Messages dissapear yet no JS errors. Each work fine on their own and inline also with Ajaxify Comments.

    And of course inline use .live 🙂

    Thread Starter tzdk

    (@tzdk)

    Forgot to say that I am still a bit skeptical towards .live in 1.8 vs. WP plugins. Some weird issues, like with http://www.themezilla.com/plugins/zillashortcodes/ which make use of .live. Plugin not avail. on .org site but if that is activated your fully jQuery 1.8 compatible plugin does not work on 1.8!

    No JS errors, there is just no message displayed. BlockUI issue then? There is a bit of smooth scrolling going on so not dead. Or is this because ThemeZilla code make use of .live -> .on fix like you fiddled?

    Using 1.7.2 and no problems. Both work. Can make one go hmmm 🙂 I am thinking general issue, dont particulary care for that plugin.

    I tried BlockUI 2.43 which is 0.01 newer than the one currently used by your plugin. No difference.

    On another test site using scripts with .live stuff and jQuery 1.8 your plugin also does not work. My first reply was almost stating your fix did not work but it does, just not under some conditions – like with scripts using .live – or something. Or is it even your fix that is a problem? Not good to report “errors” without even seeing anything in JS error console, make no sense really – but I remain skeptical to it all… I kind of hope you say OH I see! and here is a new fix because if general jQuery .live vs new 1.8 issue that is bad.

Viewing 15 replies - 76 through 90 (of 121 total)