Bill Dennen
Forum Replies Created
-
Forum: Plugins
In reply to: [Front-end Editor] [Plugin: Front-end Editor] Problem maintaining line breaksscribu, is this expected behavior for editing custom fields with the rich text editor? That is, loss of line breaks, temporarily until reloading the post.
We're also seeing a loss of line breaks when hitting "Save". If I reload the post, the line breaks are there, as expected. 1) load post 2) double-click on a custom field to edit it in NicEdit 3) hit save 4) field loses line breaks -- 5) reload post 6) line breaks are there ok.Forum: Plugins
In reply to: [Front-end Editor] [Plugin: Front-end Editor] Javascript errorChrome 11.0.696.34
Safari 5.0.4
Firefox 4.0and it’s only a problem for “rich” fields from what I can tell.
Forum: Plugins
In reply to: [Front-end Editor] [Plugin: Front-end Editor] Javascript errorThanks Scribu. I see that error in Safari/Chrome.
On Firefox, the error is slightly different. “options.controls is null”
I suspect a conflict with another plugin, but I have not yet been able to pinpoint it.
Forum: Plugins
In reply to: [Front-end Editor] [Plugin: Front-end Editor] Javascript errorI should add that the editing box never appears. After double-clicking on the content to edit, the content disappears. Using the error console in the browser, I see the Javascript error referred to above.
Thanks Things seem better when the post type is registered. No more permalink issues.
Is it proper to “temporarily” register the post type when the shortcode is called? I’m first checking to see if the post type is registered, with:
if ( !post_type_exists( 'faculty_profile' ) )If it’s not registered, I register it. If it is registered, I assume things will work.
Is there a better way to do that?
edit: saw your tweet about looking at how sitewide tags does it. I’ll take a look. thanks.
Thanks Ron. It’s not registered. But, I will try that and see what happens. I wanted to avoid it…
Thank you. I can verify that switch_to_blog works fine.
I am running into a problem with permalinks, as you mentioned. Even with Switch Site Rewrite enabled, I am seeing a problem. Basically, permalink structure is not correct, but the links do seem to work.
Forum: Plugins
In reply to: [WP Super Cache] [Plugin: WP Super Cache] .htaccess rulesthanks Donncha!
Forum: Plugins
In reply to: [WP Super Cache] [Plugin: WP Super Cache] .htaccess rulesThanks Ron. Yes, I figured that part out. But, the problem is that the htaccess rules are not showing up properly on wordpress.org! In any event, if you cut/paste from either the readme or wordpress.org, you’ll break your site. 🙂
For what it’s worth, if I enable it only for the root blog, things seem fine. The page cache seems to work even for the sub-blogs, even with the plugin not enabled for them. However, I do not get the html comments at the bottom of the page confirming this.
The reason I think it’s working: the cache files for the sub-blogs are created in wp-content/w3tc/pgcache/ and I can edit them and see the edited files being served. Weird.
But, as I write this, I am not sure this makes any sense.
Frederick, could you provide some info here? Looking for advice on a subdirectory multisite install. thanks.
Thanks again. I am running a sub-directory install. Perhaps that is the difference between my setup and yours.
Thanks for your help.
I am still confused by if/when the various htaccess files need to be updated and how. Ideally, one set of htaccess rules would work.
BUt, it looks like W3TC augments at least one htaccess file and makes it sub-blog specific.
This one has sub-blog specific statement in it. I did not add it manually, so I assume W3TC did:
wp-content/w3tc/pgcache/.htaccessI may be missing something obvious, but I don’t get how this scales.
The wording of that check box is very confusing. “deselect this option to disable all caching functionality”
it’s basically a toggle for the items below it. I think kfawcett is right, you can ignore it and just enable the parts you want (below).
It looks like the settings should be copied from the main site, upon activation, as Frederick writes here:
Thanks kfawcett. This sounds like a major pain, and I’ve not found any documentation about it, aside from what you wrote. I may need to stick with WP Super Cache.