Template Compontent: No content Box

[asap247]

Hi,

In the Template component field, I don't have a content box to enter any content. I used to have one but not anymore. I checked the screen options on top and there is no field to apply there either. I have the following information saved, I tried disabling all the plugins except pods and still no effect, its the same thing in all browsers:

Debug Information WordPress Version: 3.9.1 PHP Version: 5.2.17 MySQL Version: 5.1.73 Server Software: Apache Your User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 Session Save Path: /tmp Session Save Path Exists: Yes Session Save Path Writeable: Yes Session Max Lifetime: 1440 WPDB Prefix: wp_ WP Multisite Mode: No WP Memory Limit: 40M Pods Network-Wide Activated: No Pods Install Location: /home/metro/public_html/wp-content/plugins/pods/ Pods Tableless Mode Activated: No Pods Light Mode Activated: No Currently Active Theme: Genesis Child Theme Currently Active Plugins: Captcha: 4.0.1 Contact Form 7: 3.8.1 Content Aware Sidebars: 2.2.1 GARD Pro: 2.4.1 heatmap for WordPress: 0.2.1 Pods - Custom Content Types and Fields: 2.4 Preserved HTML Editor Markup: 1.5 Rank Tracker: 1.9 Redirection: 2.3.4 SEO Booster 2: 2.0.8 Wordfence Security: 5.0.9 WordPress Front-end Editor: 0.10 Wordpress Popular Posts: 2.3.7 WordPress SEO: 1.5.3.2 WP Lightbox 2: 2.28.8.5 WPSocialite: 2.4.1

[ghost]

Update: I tried installing the plugin on another site that is on a different host, a LAMP VPS w/WHM and cPanel, no issues at all. Based on this it seems likely to be a conflict between pods and the server. I will keep looking for possible environment related conflicts.

[ghost]

For any of you having this issue on Rackspace Cloud Sites hosting, this seems to have fixed the problem for me: http://www.rackspace.com/knowledge_center/article/cloud-sites-php-op-code-cache

I added the line... php_flag xcache.cacher 0

...to my .htaccess file and can now consistently get the Template content editor area and Pod Reference to load.

Use at your own risk, I don't have any advanced knowledge as to why this flag would be required to run pods effectively, nor any potential side effects to your sites. This may also work for other virtualized hosting setups, no way to know for sure.

We host about 60 sites in this environment with a variety of plugins and this is the first time we've had to enable this flag so hopefully this info will prove helpful for the ongoing development of pods and perhaps a coding solution can be found that will allow it to work without having to make this adjustment.

[Shelob9]

A user in the forums reports they resolved this issue with their hosting provider and were given this message:

Looks like xcache is causing the issue. The issue should be fixed for the account "XXXXXXXXXXXXXX".

If any other account is using Pods then you may disable "xcache" by going to "Select PHP Version" in your cPanel and then change the php version to PHP 5.4 (not native) and then uncheck "xcache". Once you save the settings it should work fine.```

[sc0ttkclark]

That doesn't sound like a good solution, nor recommending 5.4 or below.

[Shelob9]

@MODOKmatt @dweinlick @waywardsister @floede @jaroc We are looking for access to a server that has this issue present on it, so we can debug further, so we can investigate the strong possibility that a problem xcache configuration is to blame. One of the reasons this has taken so long to fix is that no member of our team has been able to reproduce the issue.

If anyone is willing to allow us access, please email me at Josh@pods.io or send me a direct message in Pods Slack