mattloak

@jenngood: The point of the plugin is that it allows you to track a ton of metrics that would normally be very complicated to setup manually in Google Analytics.

@joostdevalk: I agree with Jenn on the point that you should make it more clear that the plugin doesn’t display stats anywhere in the wp-admin.

Just checking in, any updates?

That worked great. Thanks!

I’m having the same problem. I’ve posted it on the More Fields support forum: https://more-plugins.se/forum/topic/bug-more-fields-not-saving-new-fields-on-input-box

thanks

Is there any way to make the post default to Private without editing core files? Can this be done with filters in the functions.php file?

I think the old sidebar is the best place, it’s a good standard. I would say more often than not, I feel the need to go to the developers website for a number of reasons before I will decide to use a plugin. I don’t want to have to go searching around for the link, the sidebar is a nice, standard and quick way to get more info on the plugin and the legitimacy of the developer.

Let me know if you figure this out. I’d like to be able to pass break a page or a post up into pages directly from the theme as well.

You need to modify your single.php file. Right now your theme is inserting the related posts before the wp_link_pages function. This is going to depend on how your related posts are inserted but you can play around and move the wp_link_pages higher up in your single.php.

Thanks for the fix!

It strips out the   too. If I enter <div id="placeholder">&nbsp;</div> in the html editor then switch to the wysiwyg editor and back again to html then the   is gone leaving just <div id="placeholder"></div>. Now if I switch to wysiwyg and back again that div placeholder is gone too. What gives?

So how do you continue an open conversation from the MU forums? Do I have to start a new topic here and just hope all the people that posted on the old thread find it?

I think using it demonstrates a lack of understanding of what W3TC already does for you.

Clearly I don’t have a full understanding of what W3TC is doing for me.

You said that W3TC doesn’t cache widgets but using a widget caching plugin demonstrates a lack of understanding of what W3TC does? How? What does that mean? Are you saying that caching widgets isn’t a good idea, or it isn’t a good idea to do when running W3TC?

Or are you saying “If you don’t know, I’m not going to tell you?”

Another question I have is which type of page caching should I use? I have memcahe installed but under the page cache method it is under the heading “Mulitple Servers” which I assume means a CDN. I’m not using a CDN but can I still choose memcache?

@frederick Townes – I completely understand. I just wanted to make sure there wasn’t some extensive documentation that I was missing. Thanks for creating this resource.

@blau – Thanks for the response. As I said I’m familiar with the FAQs. I have a number of questions that are not addressed there but mainly I’m having a difficult time with the server setup.

First of all I’m running LiteSpeed not Apache so I don’t know how that affects the installation instructions. Should I be doing something differently with LiteSpeed?

The instructions list the following steps:
– Server Preperation
– Memcached (Daemon) Installation
– PECL Memcache Module Installation
– PECL Alternative PHP Cache (APC) Installation (Recommended)
– XCache Installation
– eAccelerator Installation

I’ve got Memecahce installed but I did not install Optcode or APC because my host told me they can cause instability with PHP on LSWS.

In the instructions above am I supposed to be choosing one or doing them all? I guess I don’t understand if they are complementary meant to work together or if they are alternatives. What makes it more confusing for me is that fact that only one says “recommended.” Does that mean the others are required? If so, what’s the implications of not installing one of them? Do they render the plugin useless or just impact performance?