Peter McCormick

  • Content count

  • Joined

  • Last visited

About Peter McCormick

  • Rank
    New Member

Contact Methods

Profile Information

  • Gender
  • Location
    Cornwall, VT USA
  1. Newsletters

    False alarm. Turns out it was a skin selection thing. You can go ahead and delete this. Thx.
  2. Newsletters

    I've been using Newsletters regularly (and successfully) for a couple years now, but I've recently encountered a problem. We upgraded to a new server and skin set and now the HTML preview has no content other than the header and footer. Even the manual content blocks are empty. The plain text preview is OK. I checked the skin_newsletter templates and all are as before. Another weird thing is that every time I edit the newsletter header and/or footer HTML content, a line break is added. Save it four times and four line breaks are there. If I use "inspect element" to check the HTML preview in Google Chrome, there are several lines of <!-- isHtml:1 --> and <!--no data in this master skin--> Any suggestions? Thanks.
  3. Newsletters

    The issue resolved itself today. No idea why it misbehaved yesterday (and I tested it five or six different times). Sorry to bother.
  4. Newsletters

    I have three newsletters set up, one drawing from Forum content, one from Calendar and the other from various Content databases. They have been working fine for several months. As of this morning, when 'Previewing as HTML', the header and footer appear normally but there is no content in between. "Previewing as Plain Text" works properly. We upgraded to 3.4.4 last week. I have recached the skins, etc. Any ideas?
  5. Export Member's Emails

    It would be very helpful if we were allowed to select multiple member groups using CTRL/Click rather than only one group or all.
  6. I (sort of) understand the desire for a simple/defeatured text editor for use with forums. That said, if IPS wants Content/Blog/Nexus (wrapped around IPB) to be seriously considered as a full-fledged CMS, then at least provide the option of using the full-featured CKeditor for Content and Blog instead of the default defeatured CKeditor. I would like to migrate our blogs from Wordpress to IP.Blog, our news/article system to IP.Content and our membership/invoicing system to IP.Nexus to better mesh with IP.Board as a complete system. Content and Blog would be used by professional editors, not the great unwashed. Asking them to use the current dumbed-down CKeditor is sending them back into the Stone Age, particularly regarding image handling. Would it be a big deal to simply provide an option for full or simple editor?
  7. Why no image uploader in RTE?

    I have been using IP Board for about five years now as one component of my site (, which has also grown to include 11 Wordpress blogs all on separate installations (mostly because WP multi-site installation wasn't available at the outset) and a fairly comprehensive news article component, for which we're currently using a less-than-satisfactory RTE cobbled from Joomla years ago. I'm considering a major site revamp utilizing the entire IPS suite which would make all good sense save for the very obvious lack of a decent image uploader/resizer/alignment tool (like Wordpress has) integral to the RTE in IP.Board, IP.Blog and IP.Content. I always thought the image attachment/thumbnail insertion scheme in IP.Board was a little strange, but when investigating Blog and Content and realizing the deficiency in image uploading (a MAJOR component of any news-type site) I question whether moving to Suite makes sense. The image function in Wordpress not only includes uploading from your computer, URL or media library but also resizing, justification, CSS, setting of custom margins, links, etc. Is an RTE upgrade forthcoming?