drdamour

this worked. RE: my issue, i found that if i moved my define statements up above the security defines in my wp-config my error went away. Is this a known issue?

thanks! this issue is now resolved.

ok, it’s a corporate blog so i’ll try it on monday and report back.

one other side issue i’ve encountered. On my first attempt i was doing stuff locally before putting it in production. First, i used the UI to set the SES keys and test everything out, then after success i switched to the defines. When i did that the ses section of the the config UI told me these values were set by the administrator. it did not display them or let me edit them.

On my second attempt in production (different WPMU instance) i just updated the wp-config with the defines right off the bat. Generally this worked, but now the SES API keys section shows the keys in the config UI for every blog. The user can edit them and save them, although the UI doesn’t show the updated values, instead using the defined values from wp-config.

Any ideas? Is there a missing entry in the DB? the emails function fine, i just wanted it to act like it was in the first set up, with a message indicating that the setting was defined in the UI.

This is not resolved, i performed those steps but every site in the network still says that the ses plugin is not active. I want to activate it for every site..not just configure it. Is that possible?

/U might be more expensive, but may not matter at all. not really sure, a performance test harness would help a lot there.

I use windows live writer to generate my posts and it flattens everything to a single line in XHTML mode so that was the culprit.

I probably should start another thread, but is there a way to enable TOC in the post body on the front page but disable it (widget only) for single article views?

fyi: i fixed it by making it ungreedy on the .*

from:

preg_match_all('/(<h([1-6]{1})[^>]*>).*<\/h\2>/', $content, $matches, PREG_SET_ORDER)

to:

preg_match_all('/(<h([1-6]{1})[^>]*>).*?<\/h\2>/', $content, $matches, PREG_SET_ORDER)

per: https://www.php.net/manual/en/reference.pcre.pattern.modifiers.php

so here’s the problem.
the widget happens before certain processing takes place. That processing is putting in newlines into the content string

so for the widget, the regular expression is matching against one line of text, thus only finding one h2 tag for the entire doc, where the post body it’s finding a bunch cause they are all newlined out.

all the basic widgets work fine
there is no mu-plugins folder
is there a debug mode or something i can turn on, or logging of some sort?

running on ubuntu
apache 2. something
php 5.3.18

the dead simplest test exhibits the problem

<h2>header 1</h2>
lorem
<h2>header 2</h2>
lorem
<h2>header 3</h2>
epsum
<h2>header 4</h2>
epsum

this is a multisite, and my blog isn’t the main site.

during my tests it is the only enabled plug-in
I’ve also made it the only widget

in twenty eleven it doesn’t appear in footer either for me.

another bug

if i add the widget, check the only show as widget option, then delete the widget, the TOC doesn’t appear for any articles (post or pages). I then need to add the widget back to get the toc to appear in the post body, and as long as i don’t check the only show option the body continues to show the TOC.

clearly the option is persisted across the widget’s lifespan. adding the widget again resets the option.

just switched to coraline, doesn’t work there either.

to recap:
TOC shows fine in post body if widget is there or not
set widget to only show widget, TOC does not appear in post body
widget never appears

ok let me clarify.
twenty eleven is bad test case cause it doesn’t have a sidebar for single.php

i’be been using bloxy two

yes i’m sure i have the minimum number of headings because it displays fine in the post content. should be plain ascii or whatever the default is.

i’m happy to try another theme if you want to get a basic reference test.

i tried twenty-eleven