Jason Carter

Hi islander,

I believe that setting only applies to new pages/posts created. For existing pages go into the “all posts” section and then go to “quick edit”. You should be able to see a checkout something like “show/allow comments”. Uncheck it and the comment section will disappear for that post. You can do this on an individual case or you the bulk functionality.

Hope that helps.
Jason

Hi galder56,

It sounds like you want your contributors to write content in some type of “dev” environment and then push the content over to your live site. Correct?

Well, I’d first ask why? They are contributors and this is exactly what WordPress does already. You have publish content in phases such as “draft”. And if you’re looking for something more robust, do a google search for something like “wordpress publishing workflow” which will give you some ideas of plugins to use to control the publishing – meaning, a contribute writes an article and sets it up as “review”, then the admin or chief editor reviews and approves it for publishing.

Using content workflow or just the built in functionality of WordPress is probably what you’re looking for and will be easy for your users.

example solutions only
http://www.wpbeginner.com/plugins/how-to-improve-your-editorial-workflow-in-multi-author-wordpress-blogs/
https://ww.wp.xz.cn/plugins/oasis-workflow/

How you described going from development to production is mainly used for development work such as making theme changes or adding functionality to your site. In which case this would be done by a developer and not a content contributor.

Does that help?

Hey jmerie…okay, let’s try again. First, I’ll say there’s many ways to skin a cat and this is just how I install the wp cat.

sidenote: I’m leaning towards the config.php guy – although i’ve seen others do this, I’ve never manually edited my config file prior to install. WordPress can do it and I’m lazy so I let WordPress do it.

Getting the easy stuff out of the way:
1. download wordpress.zip, unzip and keep the wordpress folder somewhere
2. install wamp, create new db created and new user with appropriate access
3. copy the wordpress folder into the wamp root that you’re using c:wamp\www\wordpress

Now the installation (doing it as I type, so I know it works,lol):
1. from the browser go to localhost/wordpress/wp-admin
(this should take you to the install screen to pick a language)

2. follow the steps
– screen 1: “let’s go” button
– screen 2: db name, username, password, host (use ‘localhost’), table
– screen 3: “run the install” button
– screen 4: type in site details, “install wordpress” button
– screen 5: Sucess! “log in” button

3. after clicking “log in” you should now be at your login screen (localhost/wordpress/wp-login.php)

4. enter info and you should be good to go!

So you see I haven’t actually touched the wp-config.php file? But if you go into your directory, you’ll notice it’s been setup for you. If you still need to make changes, just go directly to the file and make your changes.

Personally, I’ve always installed WordPress with those steps above and then made any customizations required to config files or any other file afterwards.

Try that out and let me know what happens.

localhost/jmerie/wp-admin.php
should be…/wp-login.php
Sorry

The “white screen of death”…You’re not the first to have this problem, if that makes you feel any better 🙂 but there are multiple reasons it could be happening. Try taking a look at the below…

http://codex.ww.wp.xz.cn/Common_WordPress_Errors
http://www.wpbeginner.com/wp-tutorials/how-to-fix-the-wordpress-white-screen-of-death/

Hope that helps.
Jason

Hmm, I understand the issue much better now. You basically have an archiving problem where the data must be readily available but you don’t want access to your “active/recent” data being slowed down by the large archived data.

I’ve never come across this type of situation (with WordPress) but my gut feeling is that what you proposed seems a bit “ugly”. Design-wise and usability-wise.

I believe in other situations you would have some sort of distributed back-end where when a request came in for archived data, custom code would reroute the request to the appropriate server (or you may have a no-sql type storage). I’m definitely not an expert in this area.

Unfortunately, I don’t have any possible solutions for you 🙁

Hey EG23,

First off, I’d say moving a WordPress site can actually be very easy. You can do it manually – making a backup of mysql, etc or the easier way is to use one of the many plugins which help in this such as those in this link

http://premium.wpmudev.org/blog/8-plugins-for-safely-moving-wordpress/

That being said, a “local install” is always good practice because you get to verify the process before trying it in a live environment.

I’m not sure I understand the “register with WordPres” part, are you referring to WordPress.com? I’ve always done self-hosting so I can’t help you there.

If you’re doing a self-hosted WP site then the link provided gives some great options for moving the site. But I’d highly recommend trying it out locally first, then once you’re confident of the process, backup the live environment, start the moving process and verify (remember things like DNS settings, domain redirects, etc)

Hope that helps,
Jason

Hi Chachalady,
Not an expert but I have some experience in DB/SQL related tech and I’m hesitant to say you should do it if you don’t know what you’re doing. Do you really have that much content? Or is this a performance issue of your site and you believe “splitting” will make it faster?

In any case, it sounds like you’re looking for load balancing – if you good something like “wordpress mysql load balancing” you should get back some results that’s more targeted to what you want.

Articles I glanced at that looked interesting…

http://www.severalnines.com/blog/scaling-wordpress-and-mysql-multiple-servers-performance

https://www.digitalocean.com/community/tutorials/how-to-optimize-wordpress-performance-with-mysql-replication-on-ubuntu-14-04