Forum Replies Created

Viewing 15 replies - 271 through 285 (of 286 total)
  • Supporting WebKit would required to rewrite completely the CodePress JavaScript code. That’s why i dropped it 1 year ago on my project and have choosen an other perfect working replacement.
    During 1 year no progress has been made at the CodePress Project, it seems the initial author has stopped working on.
    Very bad for WP i’m afraid, because it produces eigther a lot of re-work with WP programmer resources or a new search for a suitable replacement.

    I don’t know why this is called “fixed” if it removes functionality!
    Sure, to run properly the blog, it should detect, that the PHP Module “Tokenizer” is not installed and disable it usage (which removes the ability to inspect WordPress documentation about WP tags found in code).
    But in my opinion this also needs a statement in this case, that you can get back this documention links (dropdown list of found tags) if you talk to your provider to get the “Tokenizer” installed.

    Please refere to my answer about the jQuery UI Tabs problems between WP 2.7 and WP 2.8: http://wordpress.org/support/topic/243942?replies=4#post-1127263

    The difference between WP 2.7 and WP 2.8 in terms of jQuery and jQuery UI is the major version upgrade of both libraries. The new one libraries are not backward compatible to stuff written for older versions.

    Especially jQuery UI Tabs has been changed (internal and also in usage).
    This is the usage at WP 2.7 with jQuery UI v1.5.2
    $(”#tabs>ul”).tabs();
    And this is the usage for WP 2.8 with jQuery UI v1.7.1
    $(”#tabs”).tabs();
    The Tabs now expects as selector the hosting div container instead of the ul list the older expects.
    If you need a 2 version safe usage, try something like this:

    //jQuery UI 1.5.2 doesn’t expect tab ID’s at DIV, so we have to apply a hotfix instead
    var needs_jquery_hotfix = (($.ui.version === undefined) || (parseInt($.ui.version.split(’.')[1]) < 7));
    $("#tabs"+(needs_jquery_hotfix ? “>ul” : “”)).tabs();

    This type of internal change in jQuery UI affects also other components so a lot of compatibility work has to be spend by authors of plugins and themes.

    The main .htaccess in WP root folder could look like this:

    # BEGIN Alexander
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^checkout/step1$ /checkout/step1.php [QSA,L]
    RewriteRule ^checkout/step2$ /checkout/step2.php [QSA,L]
    RewriteRule ^checkout/step3$ /checkout/step3.php [QSA,L]
    </IfModule>
    # END Alexander
    
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    # END WordPress

    Your own block ensures, that the urls with checkout/step1 will be translated and directed to checkout/step1.php and delivered.
    Keep in mind, that you will normally not be able to access at this php paged workpress code as long as you not launch the loader from wp.

    You could also direct all steps to one php file by giving as param like this, but please sanitize the incomming param value carefully:

    # BEGIN Alexander
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^checkout/(.*)$ /checkout.php?step=$1 [QSA,L]
    </IfModule>
    # END Alexander
    
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    # END WordPress

    where you now get at the checkout.php as $_GET[‘step’] the given step(s) like “step1” but there could also arrive some bad things, check it!

    <?php wp_dashboard(); ?>

    If you remove this, the dashboard will be empty, because this function call populates it.
    It could be that one of your plugins tries to come up with an widget for your dashboard but not supported in WP2.8 and let it crash.
    Could you please check whether you have such plugins running and deactivate those temporary for testing reasons.

    Any file with a leading dot is a hidden file in terms of unix. It’s necessary, that the file is named .htaccess and resides in the root of your WP installation.
    Some FTP programs doesn’t show initially hidden files but can be configured to do so. Than you should able to see those again.
    Please create such a file (don’t strip the leading dot) put the lines into and upload it.
    If your home PC runs Windows, you can’t locally create files with leading dot’s. So just create a htcaccess named file, modify the content and open an Windows Console. Changed to the folder containing the file and enter command
    ren htaccess .htaccess
    Then you should have one for upload. You can alternatively upload the wrong named file and rename it with your FTP program at your webspace.

    I hope, this may help you going forward.

    If you really running at 1 and 1 Server (and i think so because of 304 layout of your home site), i would try to configure the webspace to work with PHP5 instead of PHP 4.4.9 as currently reporting by requesting the login screen.
    To do that, just edit your .htaccess File in your root wp root dir (or create one if there is non) and place as first lines inside:

    AddType x-mapp-php5 .php
    AddHandler x-mapp-php5 .php

    This switches the PHP 5 on. Try this first before further steps to be evaluated.

    With the current version 1.6.0 of this plugin you should be able to columnize your post as well as pages. I have also fixed all bugs found during WP 2.8 release evaluation.

    Currently there is no way to columnize ordinary post entries, because WP doesn’t accept page breaks in posts and strips them.
    I have no proper solution for posts for now. If someone has a suggestion, how to go arround this issues, please let me know.

    I found the setlocale() issue reason and wrote an article about.
    Also at my blog it wrotes back int settings at german language locales and i also show the reason and the solution, and of cource using as example “Google Sitemap Generator”.
    http://www.code-styling.de/english/php-function-setlocale-and-numbers-can-be-damaged

    There are still hard problems remaining, if your provider has disabled the ini_set() function for security reasons. You will get a fatal error and won’t be able to edit any longer. I wrote an article: http://www.code-styling.de/english/wordpress-26-and-the-textdiff-fatal-errors
    and also a patch therefore. It has been submitted at WP Bug Trac too.

    I have tested a performant patch that solves this issue. There is a bug inside PHP implementation. Sometimes, rarely the substr() function returns wrong results even if input values are ok. Can be found here:
    http://trac.wordpress.org/ticket/5599#comment:14
    or currently as german acticle here:
    unpack errors at gettext.php
    the english translation follows soon.

    Thread Starter codestyling

    (@codestyling)

    … and because of limitation of this forum edit capabilities i have to post additional information:

    The actual WordPress version 2.5 is affected too.

    btw: 1.) owner of entries should ever be able edit their posts and 2.) i should also be able to edit the versions, if i missed one.

    Forum: Fixing WordPress
    In reply to: IE Problems.

    Hi, easy to check by editing you site in IE with MS Developer Toolbar for IE7.

    <div id=”sidebar”>

    has to be set additional at
    {
    float: right;
    margin: 0;
    }

    than it works as expected.

Viewing 15 replies - 271 through 285 (of 286 total)