Forum Replies Created

Viewing 15 replies - 616 through 630 (of 968 total)
  • Cypher

    (@cypher)

    The current options are to either show the entire post or a summary of your post.

    If you want neither, you will have to modify the wp-rss2.php file.

    Add <?php /* */ ?> around lines 34, 39 to 52.

    You are commenting out the <link> line, the <guid> line and the rest of the code that either prints the summary on the entire content.

    Not sure why you want just the title, but here ya go. 🙂

    Regards

    Forum: Plugins
    In reply to: BAstats and wp1.5.1
    Cypher

    (@cypher)

    Was the error in regards to wp_getcurrentuser() or something? If so, it’s because of the way that particular function was redesigned in 1.5.1.

    I found that the latest version of the plugin didn’t present the same problem, but it had issues of “can’t send header information” on my RSS feed which of course broke it.

    Regards

    Cypher

    (@cypher)

    Can you check to see what if anything you have in your .htaccess file?

    Regards

    Forum: Plugins
    In reply to: BAstats and wp1.5.1
    Cypher

    (@cypher)

    What problem are you having exactly?

    I got the latest version after upgrading to WP 1.5.1 and it allowed it to work, but I had an issue with it breaking my RSS feeds, so I disabled the plugin until I get more time to look at the issues.

    Regards

    Forum: Fixing WordPress
    In reply to: 1.5.1.1
    Cypher

    (@cypher)

    The new versions of WordPress are what I could call inclusive releases. That is, they are not incremental updates on previous version, so you could pretty much jump from 1.2.x to 1.5.1.1 just as someone else would jump from 1.5.1 to 1.5.1.1.

    Regards

    Forum: Plugins
    In reply to: WPPM with CURL
    Thread Starter Cypher

    (@cypher)

    The only modification that I made was to change the use of FOPEN to CURL for remote files, all local files are read/written to using FOPEN.

    Now in this case it looks like you have a directory permission issues, and I think it’s related to the change you made in regards to the user.

    Take a look at /wp-content/plugin_mgr and see which user “owns” that directory.

    Once quick fix is to set the permissions of that particular directory to 777 through your FTP client.

    Regards

    Forum: Fixing WordPress
    In reply to: 1.5.1.1
    Cypher

    (@cypher)

    Same as 1.5 -> 1.5.1.

    1. Backup your database.
    2. Delete any WP files you haven’t specifically modified. Keep your wp-config.php
    3. Upload all 1.5.1.1 files
    4. Run /wp-admin/upgrade.php

    Regards

    Forum: Fixing WordPress
    In reply to: Can I upgrade?
    Cypher

    (@cypher)

    I believe they are fixed in the latest code in the SubVersion repository. I upgraded all the way up to the May 17th version of the code to get all the fixes.

    You might want to wait for 1.5.1.1 to come out (hopefully soon) if those two fixes are critical for you.

    Regards

    Cypher

    (@cypher)

    What plugins do you use? Always start there, try to disable them and see how your site behaves.

    Regards

    Cypher

    (@cypher)

    A ‘cron’ job is a Unix/Linux functionality that allows a task to be run at a pre-determined time or on pre-determined intervals by the system automatically.

    This is usually a service that your web hosting prodiver has to allow you to do, most allow it, but some don’t. You would want to contact your webhost and inquire. There is nothing you can do on the user side to make this possible if your webhost doesn’t provide you with Cron service.

    Regards

    Cypher

    (@cypher)

    Cypher

    (@cypher)

    We assume that you are installing/playing around with WordPress 1.5.1, in that case please have the following code in your index.php file.

    To start, use a program like “wordpad” on your machine and enter the text below into it. Save it as index.php in a location you can remember, now open your FTP program and connect to our website. Then from the location on your local computer where you saved the index.php, copy it over to your website.

    The code is:

    <?php
    /* Short and sweet */
    define('WP_USE_THEMES', true);
    require('./wp-blog-header.php');
    ?>

    This is necessary to get your website working.

    Secondly, .php != .html. Let me explain.

    When you create a website and visit it with a browser, your browser talks to the web server and has to start feeding your browser some file. By default, under Apache (a free Unix/Linux web browser) this file is usually index.html (index.htm sometimes).

    This could be considered the FRONT DOOR to your website, from there you can use HTML code to direct visitors to other files and so on.

    Now let’s move to the PHP age of dynamic web creation. Here your FRONT DOOR takes on a slightly different aura in the form of index.php. Apache now has to instructed to look for this new file to get you going. WordPress is a PHP program that uses the index.php file to get started.

    Without a valid index.php, your website will be like a house with no front door.

    Other web servers and sever-side scripting languages (PHP is one of these) use different index.<extention> file. You can have index.asp, index.jsp, index.php, index.cfm, and of course the venerable index.html/htm.

    Phew..:) hoopefully that wasn’t too much information..

    Regards

    Cypher

    (@cypher)

    @dss: Your livesearch implementation doesn’t work on my Firefox 1.0.4. It does work on IE 6. The links that show up have a hover color of white which makes them disappear against the background, might want to change that.

    Regards

    Forum: Plugins
    In reply to: Gravatar Plugin No Result
    Cypher

    (@cypher)

    Did you intend your “avatar.jpg” to show up on every post or did that happen after you started playing with the Gravatar’s??

    If that is indeed supposed to be your default avatar or your gravatar, then you’ve placed the Gravatar function call in the wrong location.

    I don’t see any mention of the gravatar calls in the Comments section. Usually, there is a <img> tag with the class of GRAVATAR.

    Please paste your comments.php file into http://pastebin.com so that I can see what it looks like and help you debug this issue.

    Regards

    Cypher

    (@cypher)

    The googlebot and other search engine bots will run through your website just as any visitor would, they will go through all the links which are indeed pointers which are directed to appropriate PHP files with queries that cause the information to come from the database.

    But once the information is presented, they snapshot the information and catalog it. When you do a search for information on Google’s website they are bringing the information their vast database of knowledge. They also have a cached version of your pages.

    Having static information doesn’t lead to any better search-results as opposed to pages created dynamically. I think your confusion lies in just the fact of how you understand search engines to work.

    Regards

Viewing 15 replies - 616 through 630 (of 968 total)