Hiranthi

Thanks for catching that! I’ll get it fixed right away ??

That’s because the $prime_cols in your theme template doesn’t exist when the pre_get_posts action is doing it’s thing.

Do you have a WordPress.com or a self-hosted (www.ads-software.com) install? And are you logging in as an administrator?

You could try something like WP Table Reloaded.

Oh and could you please mark this as resolved? ??

If query_posts is getting used somewhere it’s overwriting the main query results ($wp_query). In order to get them back (and display the correct page contents) it needs to be reset (so that $wp_query has the main query as contents again).

Nacin had a great presentation about this last weekend @ WordCampNL ?? (he does have slides online somewhere, so if you want to know more about it you can check that out).

That means the main query is overwritten somewhere. Probably because of a query_posts that’s being used and isn’t getting reset (to reset the main query and display the correct content).

You should be using an array ??

<?php
if ( is_page( array(1, 2, 3, 4, 5) ) )
{
    // do something
}
elseif ( is_page( array(6, 7, 8, 9, 0) ) )
{
    // do something
}
?>

Yeah, that’s what I figured ??

If this has answered your question, could you mark the topic Resolved? ??

What’s the reason of not transferring the website to your server? I mean, if you have to install WP for the client, the contents would have to get in there too, right?

So, I guess you mean that you don’t want them to transfer the domain to you? In that case I would change the DNS of the domainname (adjust the IPaddress it points to, to the IPaddress of your server) and just setup the WP site on your server (assuming this is possible).

If that isn’t possible a lot of domain providers give you the possibility of using a frame redirect (which I wouldn’t recommend btw, but if there really is no other way..).

I’m not quite sure what your first question is, since in your first sentence you mention you have to use WordPress and in the second you are unsure if you should use WordPress for it. So, without going into your second paragraph: your first line says you should use WP ??

So, to the second paragraph: There are a few ways to build multiple galleries. To use multiple built in galleries you should use different posts. You can also use a plugin like NextGen Gallery and setup seperate galleries in there.
You can style it however you want. If you’re using the posts solution you could add classes in the loop (ie gallery-1,gallery-2 etc.) or use CSS-only (ie .galleries:nth-child(1), .galleries:nth-child(1)).
When using a plugin like NGG you can use seperate divs and load the specific galleries inside that div (how to do that would be somewhere in the docs of NGG, haven’t used it in a while so I can’t remember what the shortcode is).

So, yes: you could use WordPress for this.

WordPress saves the password encrypted, so you wouldn’t (shouldn’t) be able to retrieve the actual password (if you can do that, others can do that and thus the website would be in danger).

Personally I’d request the username (or just password) again, similar to LinkedIn requesting the password again when making changes to the profile.

Have you tried accessing through https://www.meltingposts.com/feed/?

I get the feeling you’re misunderstanding me. I had to disable the plugin to get the code to be displayed properly, I didn’t disable it just for fun.

The WP Syntaxhighlighter plugin is adding htmlentities to the entire post-contents, which makes it extremely hard to read on the frontend (and backend too). Extremely annoying.
I had to disable the plugin to turn the entitized (or whatever it’s called) characters back to what they had to be (< > ‘ & etc) and then enable the plugin again to get the highlighting on the frontend back.

So: with the plugin enabled all < in the post (whether they’re inside pre-tags or not) are getting changed to &gt ; (minus the space ofcourse), which also affects the frontend (since everything inside pre-tags are getting displayed as is). But: when I disable the WP Syntaxhighlighter plugin code between pre-tags aren’t getting changed.
I have also tested with WP Syntaxhighlighter enabled and other pre-plugins (as in: plugins that preserve the code within the pre-tags) disabled but that didn’t work either. The only thing that works to keep the code between pre-tags formatted as it should be is with disabling WP Syntaxhighlighter.

And as I already mentioned in the OT: I didn’t use the Visual Editor.

Hi Cass,

You need to put that code inside the wp-config.php of your WordPress install, not a file in your theme. The wp-config.php is usually in the root of the site (ie public_html).

Regards,
Hiranthi