Forum Replies Created

Viewing 15 replies - 91 through 105 (of 383 total)
  • Thread Starter ringmaster

    (@ringmaster)

    @brad:
    If you click the folder graphic (not the text) that contains the images, it’ll add all of the images directly inside (not recursive) to the post.
    I was cutting and pasting names, so, ok… 🙂
    @noise:
    Maybe it’s your client plaform? What browser OS are you accessing from? Through a proxy? Have you customized WordPress authentication in any way? Do you have a non-standard directory installation (like, virtual directories to host the WP stuff, or a multi-host setup)?
    I’m just trying to think of any reason why the security info wouldn’t pass through to the file picker.
    Try this- Go into the file exhibit10f.php and look for this line near the top:
    if($user_level == 0)
    Change it temporarily to:
    if(false)
    You’ll want to put this back to prohibit unrestricted access to your image directory.
    See if the picker works. Try uploading a file. If things stay OK, it might be worthwhile researching another method of authentication.
    @rog:
    Glad it’s working. I had a feeling it was a version issue. 🙂
    @razorhide:
    Yeah, 1.3 changes the scope of a few things in plugins regarding configuration options. So certain things would work in certain places (like the file picker), but not others (the post editor). Or vice versa. Anyway, the 1.1d2 upgrade should temporarily address these issues.
    @nacron:
    It’s showing forbidden in the file picker area?
    The files in the exhibitimg directory need permissions, too. Specifically the exhibit10f.php file. That’s the file picker. If you access it directly (not on the post page), you should see an “Unauthorized” message. If you’re seeing a Forbidden/403 or Missing/404, something’s funky on your server and you’ll need to mess with permissions/settings until you can see the picker or the “Unauthorized” message.

    Thread Starter ringmaster

    (@ringmaster)

    Ok…
    @brad Jones, Rog32:
    You can do what Rog is asking. I don’t know why the individual thumbnails are not working on his setup.
    On my test site, I have a WP 1.2 Mingus installed, with the latest Exhibit 1.1d (not 1.1d2), fresh from the archive, with no modifications other than the table that the data is stored (in my database the table is wp_photos not wp_exhibit, since I started with Alex’s wp-photos plugin before I wrote Exhibit). Be sure that you’re using the latest version, since previous version may not have had some of these features.
    You’ll note that the post on the home page looks exactly like the post by itself (this is done with the < !--exhibit:preview_like_single=1--> tag). Thumbnails do not display as the default because I used a< !--nothumbs--> and a < !--exhibit-thumbs:#-#--> for each of the inline thumbnails.
    Keep in mind that virtually any option that appears in the config file can be set using the exhibit tags for an individual post!
    As I mentioned, Exhibit was a replacement for Alex’s wp-photos hack, and I already had some < !--nothumbs--> in my database, so I kept that feature. I should add an item in the dropdown that turns off thumbnails for posts. I will add it to the config file in the next release so that you can also set it globally.
    @noise:
    The “Unauthorized” is an Exhibit-generated error that occurs when you try to access the file picker as a 0-level user.
    This is the first time I’ve heard of anything like this happening, and I would have expected you to see other PHP errors in addition to this message if you were appropriately logged in.

    Thread Starter ringmaster

    (@ringmaster)

    There is a space “…thumbs:1-1HERE“. That won’t work if it’s there. Are you sure it’s not? My aasumption is that you’ve cut and pasted and only added spaces between the <s and the !s.
    A link to the page output would help verify this.
    Note to self: A better regular expression might obviate this problem.

    Thread Starter ringmaster

    (@ringmaster)

    And at the risk of being suddenly too verbose, here are some plans regarding Exhibit and my WordPress development, which are subject to change.
    Also, a link to the alpha-4 fix is there.

    Thread Starter ringmaster

    (@ringmaster)

    Drat. That was me. (New computer, no cookies…)

    Forum: Fixing WordPress
    In reply to: .htaccess

    It might be helpful for debugging to add an R to your flags on your rules, such as:
    RewriteRule ^index.php/archives/category/(.*)/(feed|rdf|rss|rss2|atom)/?$ /wp/wp-feed.php?category_name=$1&feed=$2 [QSA,R]
    Then when you access the clean URL via a browser, the server will return a 302 error to redirect you to the crufty page URL, thus you can use the address bar to see where mod_rewrite wants to redirect you and troubleshoot it a little better.
    (So when you put http://stonegauge.com/index.php/archives/2004/10/16/ive-failed-you-rebecca-mckinney/ into the address box, it should change to something like http://stonegauge.com/index.php?year=2004&monthnum=10&day=16... and you’ll see what it’s trying to do.)

    The method that chuyskywalker described works but does an OR on the categories. So cat=11,12 would display posts from categories 11 or 12.
    As far as I know, there isn’t a way to diplay only posts that belong to two specific categories. Are you sure you want what you’re asking for? This would be like asking for posts from “Football” and “Vacation” categories.

    Thread Starter ringmaster

    (@ringmaster)

    My original message only applies to the 1.3 blog I have currently installed.
    I don’t want static pages.
    I want to display all posts in the main content area except for those in one specific category. On the same page in the sidebar, I want to display only the last 3 posts from that same specific previously-excluded category.
    I want a running list of links and I don’t want to use the WordPress link manager. I want to run “asides” actually aside from the main content.
    Moreover, I want to know the correct way to implement querying a set of posts for display using the new WP_Query object. The object seems to cause a couple failure issues when you use it more than once on a page, so I thought I would bring these to light, since it’s possible I’m doing it wrong.

    Although this shouldn’t cause the issue, you’re not really supposed to have an “archives” directory. I mean, you’d never be able to access anything in it provided that your mod_rewrite stuff is configured correctly.
    But it doesn’t look like your rules have taken. I think I know why…
    You’re on a Windows server! Windows 2000 doesn’t have mod_rewrite!
    You need Apache and mod_rewrite to use the mod_rewrite rules as-is.
    You have two options:
    1) Wait for WordPress 1.3 and use the new pathinfo stuff (you’ll have to set your 404 page to your index, but that’s easier to do on Windows).
    2) Buy some software like ISAPI Rewrite and use that. You’ll have to tweak the rules from what WordPress provides, though, since the syntax is slightly different. I use ISAPI Rewrite on my box, and it’s good.
    Otherwise, you’ll have to stick with the crufty URLs. Sorry. 🙁

    Thread Starter ringmaster

    (@ringmaster)

    The explicit text ‘class="adhesive_post"‘ is never going to appear. It’s done through javascript. Of course, the script that’s supposed to appear isn’t appearing either.
    Some guesses as to what might cause this:
    The script is inserted via a filter on the_content(). If you’re not using the_content() in your template, this filter won’t be called.
    Alternatively, some other means of removing the sticky data from the post was employed. It’s possible that some other plugin or function you’ve got going has removed the “sticky” information from the post after adhesive has added it.
    If all else fails, you might be able to add some code to your template to test if a post is sticky:
    <?php if(in_array($post->ID, $sticky_posts)){
    //Post is sticky
    echo ' class="mystickyclass"';
    } ?>

    You could try something like that, perhaps. This code is untested, though, so I’m not guaranteeing that this will work, but it looks good.
    Nice looking site, BTW. 🙂

    Forum: Fixing WordPress
    In reply to: Reading Options

    Were all of your Blogger posts imported onto the same date? My uneducated guess is that the importer borked and imported all of your Blogger entries as the same day.
    In that case adding a new post on a new day would make the Show 1 day option show only that last post.
    Just a thought. URL?

    In order to use the mod_rewrite rules, you need to have mod_rewrite enabled on your server and must have written the rules to your .htaccess file.
    A simple explanation:
    When your web server (usually Apache) receives a request for a page, it funnels the URL through mod_rewrite first before determining what file to serve. mod_rewrite compares the URL to a list of rules (these are in your .htaccess file) and modifies the URL based on those rules.
    A rule could cause a URL that reads:
    http://www.example.com/archives/my-first-post
    To become:
    http://www.example.com/index.php?name=my-first-post
    The parameters are passed to WordPress, and your post is found and displayed!
    To create your .htaccess file in WordPress 1.2, you should go to your Options->Permalinks page and fill out the form there to your satisfaction. If you don’t want the “index.php” in your URL, don’t include it – you don’t need it! Grab the code that WordPress generates and save it as a text file named “.htaccess”. (Use Notepad!) Upload this file to the root (where your index.php is) of your blog.
    Hopefully, this will enable your mod_rewrite settings and you’ll be able to use spiffy cruft-free URLs!
    If it’s not working, first verify that you have the mod_rewrite rules copied and uploaded correctly. Sometimes this is difficult because files that start with a dot aren’t visible by default on Linux systems.
    You should also check that your host supports custom mod_rewrite rules. Sometimes they turn off this option for hosting plans in the name of “security”. There are plenty of hosts that don’t do this.

    Thread Starter ringmaster

    (@ringmaster)

    @guacamole queen:
    Well, if it has stopped entirely, then you may have mistyped something. Be sure that there are double bars (||) between each element in that statement, just as I have it.
    @benjy:
    The “adhesive_post” classname is added to the sticky post via javascript when the sticky post appears. All you should need to do is add the appropriate styles to your stylesheet for that classname, and it should work.

    Thread Starter ringmaster

    (@ringmaster)

    Ok, so I wrote some code:
    <?php
    if(!preg_match('|\bcat=|i', $query_string)) {
    $query_string .= '&cat=-5';
    }
    $posts = query_posts($query_string);
    ?>
    <?php if ($posts) : foreach ($posts as $post) : start_wp(); ?>

    This fixes my problem but brings more questions to mind:
    Isn’t it inefficient to do the unused query in wp-blog-header first?
    This code seems to cause a problem with the category cache. The update_category_cache() function gets called twice and all of the categories for each post are doubled up. So when they’re displayed, the category should read “General” but instead it reads “General General”. I think this is a problem with update_category_cache() not clearing the cache before it starts storing the values. At least, adding a line to clear the cache fixed the issue.
    After I got this to work, I used a second loop (I set $query_string completely myself for this one) to display the latest 3 posts from category 5 in a different location on the page.
    Anyone else have thoughts on this? Is there a better way to do it?

    Forum: Fixing WordPress
    In reply to: 7/9 pings

    I liked the option to ping only specific posts. The benefit is that I know that cnn.com is not going to respond, whereas another WordPress blog might.
    Also, it might be nice to have this option in the Press Post popup, which just sits there for a while waiting for the pings to complete.

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