Bug #8131
closed
- Status changed from New to Assigned
- Assignee set to Boone Gorges
- Target version set to 1.10.19
Can I get more information about how the plugin is not working?
We stopped updating the plugin some time ago because the plugin changed its slug, which means that we would have to crawl through all sites to switch them to the new plugin. I'll do that for this release.
(Marilyn, don't ever enter your Commons credentials into a site whose URL is not *.commons.gc.cuny.edu, or a domain that you know to be mapped to the Commons.)
She wrote "I was able to create a newsletter this morning, but when I wanted to preview it, the page did not load." I tried as well. I just get a blank page when I click on Send/Edit.
She reports that she'd be fine using a different plug-in with the same functions. Any suggestions?
(Don't worry! I haven't and never would.)
I've attached a screenshot of what I see when I try loading the 'Save/Edit' section of one of these newsletters. Is this what you mean by "blank page", or are you seeing something different?
What I'm seeing appears to be a timeout. I haven't dug into it any deeper than that. I'm going to upgrade the plugin as part of today's release, and I'll test again at that time. If there's still an issue, I guess I'll try to see what is going on.
No, I've attached the "save/Edit" before and after screens now. If the upgrade works today, great. If not, she'll try something else.
- Target version changed from 1.10.19 to 1.11.1
The plugin is updated but the page is still not loading. I'll look more closely into the problem when I've completed my release procedures.
I've found the problematic line in the Newsletters plugin, but I'm not really sure of the root cause. When loading a Newsletters page, the plugin does the following:
set_time_limit( 0 )
. For some reason, this is causing Apache to time out on our server. I've tried debugging and researching the problem, but I haven't had any luck. For the time being, I'm commenting out the line, and the plugin works. It's a fix we'll have to reapply the next time the plugin updates.
Can you please verify that things are working now?
- Status changed from Assigned to Resolved
- Target version changed from 1.11.1 to 1.11
Great, thanks! Moving this to 1.11, since the fix is in the repo.
Also available in: Atom
PDF
