Cannot create new email

[bret.miller]

So I just upgraded to 3.0.2. Many things changed, so I took the time to upgrade my themes. But things are not working. Here’s what I do:

Sign in to /wp-admin
Click Newsletter > Newsletters
Click “New message”
Select my theme
Click Change theme (this much works)
I click the tabs to review the previews. There are no options
Click “Create the email” (I assume this is what I should do next because there is nothing else on the page to do.)
I get a blank page. The path of the page is /wp-admin/admin.php?page=newsletter/emails/new.php. There are no javascript errors. Chrome shows nothing between the admin bar and the footer except an html comment indication that wp-content should go there. So tomorrow when I go to send my weekly newsletter out, I will not be able to do so since I cannot get past the compose page to create the email. Just to check, I repeat the process using the “default” theme with the same results–blank page. So I assume this is not my theme’s fault… I do not override “default”, just create my own two themes.

HELP please.

 

[Stefano]

The page should reload and open the editor. Go back to the email list and you should find the newly created email. Open from there.

Do you see a totally blank page or a page with wordpress menu on the left?

Stefano.

[bret.miller]

There is wordpress menu on the left, but nothing in the main area at all.

[Stefano]

So you blog has some javascript error that blocks the execution of the redirect. From email list you should be able to enter the newly created email.

What’s strange is that from version 3.0.1 a message should appear in the center of the page indication to click a link to proceed if not redirected.

Stefano.

[bret.miller]

Yes, I can go back to the list and edit the new email from there. No javascript error is displayed in the console. In reviewing the page source, I notice that the newsletter script that attempts to add a function at document load is run before jQuery is loaded by WordPress. Perhaps it would be better to insert that code immediately before </head> as opposed to immediately after </title>. Doing it so early could cause issues if other scripts aren’t as well-behaved…

It’s just a guess since obviously the code is there but isn’t executed.

As far as the link, I can see why it isn’t displayed. It is being added to the admin bar in the “Howdy…” account menu.




<li id=”wp-admin-bar-my-account” class=”menupop with-avatar”><a class=”ab-item” tabindex=”10″ aria-haspopup=”true” href=”http://update.gci.org/wp-admin/profile.php&#8221; title=”My Account”>Howdy, support<img alt=” src=’http://0.gravatar.com/avatar/2105b8a16b84bc0f4277460dafafe562?s=16&amp;d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D16&amp;r=G&#8217; class=’avatar avatar-16 photo’ height=’16’ width=’16’ /></a><div class=”ab-sub-wrapper”><ul id=”wp-admin-bar-user-actions” class=” ab-submenu”>

<li id=”wp-admin-bar-user-info” class=””><a class=”ab-item”     <script>

location.href=”admin.php?page=newsletter/emails/edit.php&id=188″;

</script>

<div class=”wrap”>

<p>If you are not automatically redirect to the composer, <a href=”admin.php?page=newsletter/emails/edit.php&id=188″>click here</a>.</p>

</div>

 

[Stefano]

Uhm, looking at your code a see an open A that is not closed and contains the javascript code (this is why it is not executed).

What is that <a class=”ab-item”?

Stefano.

 

[bret.miller]

That is part of the admin bar. It should read something like what I pasted below (from another admin page). I’m not sure how your code gets smashed on top of the admin bar. That’s the only place I’ve seen it misbehave. You can get a copy of the whole problem page here: http://files.gci.org/new-email-blank-page.htm

<li id=”wp-admin-bar-user-info” class=””><a class=”ab-item” tabindex=”-1″ href=”http://update.gci.org/wp-admin/profile.php”><img alt=” src=’http://0.gravatar.com/avatar/2105b8a16b84bc0f4277460dafafe562?s=64&amp;d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D64&amp;r=G&#8217; class=’avatar avatar-64 photo’ height=’64’ width=’64’ /><span class=’display-name’>support</span></a></li>

<li id=”wp-admin-bar-edit-profile” class=””><a class=”ab-item” tabindex=”10″ href=”http://update.gci.org/wp-admin/profile.php”>Edit My Profile</a></li>

<li id=”wp-admin-bar-logout” class=””><a class=”ab-item” tabindex=”10″ href=”http://update.gci.org/wp-login.php?action=logout&_wpnonce=df828c983d”>Log Out</a></li></ul></div></li>

[Stefano]

Can you try to disable wcache temporary?

Stefano.

[bret.miller]

Yes, it appears that Newsletter and Quick Cache are not compatible. Deactivating Quick Cache fixes Newsletter, but I can’t run without good caching or the server runs out of memory too often. At least we know what is causing the problem and how to work around it.

[Stefano]

I’ll look at the quick cache plugin: it probably is using the php buffering on administrative side and Newsletter must use it as well to capture the theme output. Probably the two are incompatible.

Stefano.

[Stefano]

They say:

By default, Quick Cache does not serve cached pages to users who are logged in, or to users who have left comments recently. Quick Cache also excludes administrational pages, login pages, POST/PUT/GET requests, CLI processes, and any additional User-Agents or special pattern matches that you want to add.

But clearly something is happening…

Stefano.

[Stefano]

If possible try to deactivate the quick cache optimization of js and css on admin side. I’m looking if somthing must be done in my plugin as well…

Stefano.

[Stefano]

Ok, I found the problem. Will be fixed on version 3.0.3… if the patch will work…

Stefano.

[bret.miller]

Thank you.

[Author]

Posts