Forum Replies Created

Viewing 15 replies - 91 through 105 (of 225 total)
  • you should be able to use the RSS import in your local blog, since that imports an xml formatted file.

    Are the rules for brands, ads, slogans requests for actual physical directories ?

    if not, your rules will need to be before the WP rules, not AFTER, since the wp rules will intercept everything that’s not a physical directory or file, they may just work fine if placed at the top of the .htaccess file rather than after the WP rules.

    second, you might try something like
    RewriteRule ^brands/(.*)/(.*) /brands/?b=$1&l=$2
    to eliminate all of the iterations of different letter and number combinations.

    use the HTML view in the editor, and add as many <br /> or <p /> tags as you want for extra whitespace.

    ps. you may also need to alter each table that exists already, since they won’t be changed with the alter db, also, you could re-compile mySQL using
    ./configure --with-charset=utf8 --with-collation=utf8_general_ci if it’s your own box. by default it’s compiled with latin1_swedish_ci unless you tell it something else (many hosting providers don’t specify this, so that’s where you end up with the swedish issue.

    I’m not exactly sure why (could just be because the SQL used to create the WP tables etc. doesn’t spell out the charset/collation for each table, and somewhere burried deep within the bowels of MySQL lies a ‘fallback’ default of latin1_swedish_ci. I’ve run across the same issue (not only with WP) generally I do the following:

    ALTER DATABASE
    db_name DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci

    that said, I’ve never run across an error like you’re talking about, everything seems to work OK without doing that but if folks dig in they’d likely find the same situation. my “my.cnf” also sets utf8 as default, so again ,me thinks this is a MySQL issue…

    looks like an issue with the width settings in your theme’s css file. Try adjusting the center/main column width settings to make it a few pixels or percent smaller.

    you should be able to integrate simplegal, coppermine or gallery2 with your WP site with equal ease, depending on your requirements. Coppermine out of the box offers the ‘bridging’ module if you wish to use a single sign on.

    you could also take a look at the wp-plugins area, there are a couple of gallery plugins available (although most of those won’t likely fit your needs since they’re simply not as powerful as something like coppermine).

    So I’m guessing we can tag this one resolved (done). I’ve upgraded just north of 20 production sites for clients from 2.0.2/3 to .0.4 without issue.

    It appears than many of these problems are related to the specific server configuration (ie. versions of things like Apache MySQL, OS, etc) rather than WP directly.

    the simplest soulution is to uninstall WP from the current location, and install it into the root directory of the web site.

    slightly off topic, but Adsense doesn’t like you ‘overloading’ a page with Adsense content, so if you tried to do something dynamic like insert the adsense code more than once (eg. in *random* comments or posts) the Google Adsense backend is sophisticated enough to not allow itself to be called more than x times per http request for a particular URI, when this happens they don’t send you any ad content for that particular request.

    working with a couple of other platforms we had tried a couple of times to acomplish something similar, and what would happen is that once a particular post or ‘thread’ of a discussion for example became lengthy because the *random* placement was called more times than Google allows all ads dissapeared from that particular page/thread.

    personally, i’ve chosen (with WP at least) to insert clients adsense code by hand into a customized sidebar.php and header.php, we have several versions of each file within the themes used, then depending on the page content different amounts or types of ads are displayed.

    food for thought…

    First, did you back up all of your old files and database as instructed before the upgrade ?

    I’m assuming you did since I just took a look at your site and it appeared to be working so I’m guessing at this point you backed down to 2.0.3.

    and the randomb.php file spit out tip number #16 when I hit that.

    if you have backed down to 2.0.3 you can email me directly at chradil@gmail.com and I’ll see if I can assist with the upgrade, it’ll be easier via email than using the forum.

    as far as the ‘randomb.php’ page, you might consider using one of the ‘random quotes’ plugins for WP instead. It sounds to me like an issue with the randomb.php file, not WP related.

    I’ve upgraded just over a dozen sites since 2.0.4 release with no problems whatsoever.

    take a look at http://guff.szub.net/wordpress/template-tags

    you’ll need to customize/code around the comment tags instead of the ‘author’ tags (although one of the author tags may return the ID of the comment author since all users are registered on your site, so you could use that instead). I’d probably start with <?php comment_author_rss(); ?> and feed that to a bit of php/html which uses it to build a link to call the author.php page with the name in that format as the “slug”.

    first, in your theme’s directory, make a copy of page.php and call it something like special-page.php.

    You can then edit special-page.php and hardcode a different stylesheet, header, etc as needed, plus make whatever other changes to the page that you need to.

    the key to the template file you’ve just created is:

    <?php
    /*
    Template Name: Special Page
    */
    ?>

    at the top of the file.
    see http://codex.wordpress.org/Pages#Page_Templates for more details.

    you then call the page with a template tag as follows –

    • is_page('special-page') represents a ‘page slug
    • is_page('Special Page') represents the page’s title
    • is_page('17') represents the id of the page
    • more examples on calling the ‘special’ or custom template are available here :
      http://codex.wordpress.org/Conditional_Tags

    wp-plugins.net and dev.wp-plugins.org currently contain the cutting edge of what’s happening with plugins.

    be sure to install he latest (2.0.4 as of this writing) version of wordpress and keep it up to date.

    each plugin’s description should let you know whether it will operate correctly with wp 2.x.x or if it is a 1.x.x plugin (many of those even work with a minor bit of tweaking).

    Personally, I’ve used phpBB for a couple of sites for years, and the WP plugin system is much easier to deal with for one, and is much more secure/less apt to cause problems than phpBB.

    I can recall a couple of times where users requested I install specific phpBB plugins which not only didn’t work, but also ruined the base installation because as you should be aware, many of the phpBB plugins ‘edit’ core system files and database tables whereas WP plugins do not, thus making them much safer and easier to use right off the bat. For example, if you installed a plugins that for one reason or another didn’t work correctly with your site (I just did one yesterday out of the dev trunk, and the site became a blank white page with one

    • tag in the source !) simply delete the plugin’s file/directory from your wp-content/plugins directory and you’re back up and running.

      Quite the contrast to something like phpBB where you’d then need to go back and by hand figure out which phpBB files were changed by the plugin, what changes were made, then attempt to return the files to the state they were before the plugin install.

      Summary — overall, you’ll find the WordPress plugin architecture much safer and easier to deal with than many other packages out there since plugins do not alter core system files

      …..c

Viewing 15 replies - 91 through 105 (of 225 total)