Lately I have noticed that when I edit or add a page the page becomes a post upon publish or update . As soon as it’s published I have to change the post type from “post” to “page” and then only is the “page” is back.
I have also noticed a related issue.
My contact form 7 created forms would disappear. When I looked at my posts all my forms have become posts. This only happens when I edit, update or create a new form. Odd.
I hope you can assist me.
Regards
[Moderator Note: No bumping, thank you.]
]]>When looking at the wp_349_options to wp_1110_options I see that 99% these blogs have a url something.kissonthefirstdate.com. These are all spam and I want to kill all these records associated with kissonthefirstdate.com
How would I go about doing it?
]]>I have a muti site install. I have one blog that I want to migrate to single install for a client. I have downloaded or exported the XML files of the blog. The new host tells me that the database for this blog is also required.
I have no clue how to backup and download only the database for this one blog on this multi install.
I have two questions?
1) Is it possible to download the database for one blog – where the blog is part of a muti install?
2) Can I blog be effectively exported and re imported only from the XML files? Or is there another way to re-create this site on a single install?
Regards
Johan
]]>The original blog works fine. The new blog lets me see its homepage when I visit the root of its directory (i.e. www.originaldomain.com/newinstall).
However, for all other pages (e.g. those produced dynamically by the install like www.originaldomain.com/newinstall/post) I get a 404 from the original install (with its original theme skin, etc.).
I can’t see what’s wrong.
The root index.php directs to the original installation’s folder:
/** Loads the WordPress Environment and Template */
require('./wordpress/wp-blog-header.php');
?>
The /newinstall/index.php directs to its own blog-header:
define('WP_USE_THEMES', true);
/** Loads the WordPress Environment and Template */
require('./wp-blog-header.php');
The settings all have the correct URLs to their own folders.
I wonder if there’s some sort of htaccess issue or something else I’m not seeing.
Is there anyway I can debug this, e.g. by looking at the exact handoffs taking place as the requests are made? I haven’t debugged WordPress before to that level.
Thanks!
]]>One will be for the blog.
Another for projects.
And one for links.
The child pages will be duplicated many times and all of them should categorize properly into their respective parent page.
So, you wouldn’t see blog posts or pages anywhere in the projects parent or child pages or the links parent or child pages.
I’m not sure how to go about this with one installation, because of the possible need for 3 different themes and 3 separate chunks of pages. Would it be better to install 3 instances of WordPress on the same server and just manually create a static top nav for the blog, projects and links and then manage the 3 through one admin panel?
Or can it easily be done with just one installation of WP?
Thanks for any help you can give me.
]]>Can somebody please provide me with the information as to how I can install 4 instances of wordpress, one one domain, that all use the same User Database. I want users to be able to go from one blog (so one install of wordpress) to the other without having to sign into a new account.
Thanks alot in advance!!
Sam,
]]>I’m planning to install WordPress on Linux system for my company website, does this scenario works with WordPress ?
Single WordPress install but can have multiple domain eg:
www.team1.com
www.team1.com/product2
www.team1.com/product3
www.team2.com
www.team2.com/product2
.
.
.etc
do i need to perform multiple install of WordPress or Apache can do it for me ?
any kind of help and assistance in setting up WordPress for hosting the website in the DMZ would be greatly appreciated.
Thanks.
]]>I want to do the following:
I already have a wordpress running in the root. I want to create a sub-directory “premium”, it’s supposed to be a exact copy of the original site, except a few changes in the layout and it will be password protected by apache. I tried doing that, but in the admin section of the “premium” install the links to posts goes to the original site, like site.com/news and not site.com/premium/news. Also, the “premium” index loads the design but it the content is 404. The “premium” version uses the same database and the same tables of the original, and wp-config is also a copy.
So, I want to know, how can I fix that.
]]>