kallywag

I have the same issue and I just found this fix. I had my ‘default page’ in google analytics set as index.php before the site’s root was live. Anyway, I removed that and I’m assuming it will fix it (need to give it some time to make sure). Good luck!

Where would I find the function reference for the various parameters I can pass to WP_Query? Your example showed two possible parameters (showposts & cat) but are there others? Where are they listed? Is there one that can specify a ‘static’ page so, for instance, you could pull in ‘static’ wordpress page content into a blog post page or the main blog page? I looked at the WP_Query codex page and it didn’t seem to list them, but I’m guessing these parameters are not specific to WP_Query.

That worked great. Just for anyone finding this post, what I have accomplished is pulling in blog post content into a ‘static’ page template so that I have static content and blog content on the same page. Here is the code I used with both loops, the first being the blog content loop and the second being the standard page template loop for static content:

<?php $my_query = "showposts=3"; $my_query = new WP_Query($my_query); ?>
<?php if ($my_query->have_posts()) : while ($my_query->have_posts()) : $my_query->the_post(); ?>

	<!-- standard tags to display blog post information like the_title() here -->

<?php endwhile; // end of one post ?>
<?php endif; //end of loop ?>

<?php if (have_posts()) : while (have_posts()) : the_post(); ?>

	<!-- standard tags to display the static page information like the_title() here -->

<?php endwhile; endif; ?>

Same problem here. I wasn’t sure if it was a WordPress problem or something my host had messed up because they’ve been pretty stupid lately.

@sideiron: the solution you linked to from itmilk.com worked for me as well.

summary: make sure the URL you have set for wordpress(and blog) in the ‘Options’ tab is the same as the URL you may have your .htaccess file redirecting to.

For me, I was redirecting https://www.domain.com to domain.com, but in the ‘Options’ tab I had my WordPress URL set as https://www.domain.com, which was throwing off the AJAX script for deleting posts/pages.

Any mod_rewrite gurus out there that could take a stab at this?

My thinking here is that the HTTP_REFERER condition should rewrite any requests coming from www.ads-software.com to mydomain.com/welcome/ which would then trigger the wordpress conditions and rewrite it to mydomain.com/index.php, which would then figure out via php how to display the /welcome/ page. Somehow it’s getting stuck in a loop though. Here is a slight modification that actually works to forward www.ads-software.com traffic to a non-wordpress file (indexold.html):

RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_REFERER} wordpress\.org [NC]
RewriteCond %{REQUEST_URI} !^/indexold.html$
RewriteRule .* /indexold.html [L,R]

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Yep found that out as well, but I opted for RewriteRule in the end so I could make use of conditionals.

@handysolo

A) Yes I had to edit my reply several times because the auto-formatting was removing bits from my code examples.

B) see the second sentence of my reply: “I have WYSIWYG editor turned off”

I’m assuming you misread ‘have’ for ‘hate’, but if not, I don’t hate the WYSIWYG editor, I just want to be able to turn off auto-formatting, and turning off WYSIWYG does not seem to be totally doing that, as evidenced with <input> fields in this case.

I’m having the same problem with WordPress 2.1 — every <input> tag I put on a page is getting a <br /> tag attached in front of it. I have WYSIWYG editor turned off. So I put in this code:

<p>Some text <input type="text" name="field" /></p>

and WordPress outputs this code:

<p>Some text <br /><input type="text" name="field" /></p>

Does anyone know the reasoning behind not offering a true HTML view for post entry anymore? I’m sure there’s a reason, I just can’t figure it out. It seems to me that if someone wanted their input to be auto-formatted they would use the WYSIWYG view and if they wanted to enter their own HTML they’d use HTML view. The question is then why would anyone be entering data in the HTML view if they wanted it to be auto-formatted?

I can’t use double quotes if my javascript call is in an attribute because it would mistakenly signal the end of the attribute value:

<a href="/blah" onclick="dothis("param","param2"); return false;">Link</a>

NOTE: For reference, this particular WP install was done just a few days ago with the latest release (2.1.3).

air0day, I have the same issue. I tried several different syntaxes to set up an individual redirect, but I’m getting the 500 error. I tried these that I found in tutorials:

• Redirect permanent /oldpage/ /newpage/
• redirectpermanent /oldpage/ /newpage/

I’m going to try to read up on apache directives to figure this out, will post back if I do.