We have installed the newest version of NSM Publish Plus version 1.1.0 and we are using version 1.6.7 of Expression Engine.

We have run into the following issues using Publish Plus:

1. If NSM Publish Plus is not enabled for a site, (we have multiple sites) the following error message is displayed in the CP:

Notice: Undefined index: kill_preview in serverpath\system\extensions\ext.nsm_publish_plus_ext.php on line 1280

2. We setup several fields with the format set to none. I discovered that if these fields contain text with characters that are not readily identified - such as the dash character created by Word - when that field data is saved with the draft, it causes an error in the CP the next time you attempt to edit that entry. After further investigation using the var_dump on the data retrieved, the Draft_Data field contains the classic black diamond with the question mark where those unreadable characters occur. The draft(s) affected are displayed with incomplete information and the following error messages are displayed in the CP:

Notice: unserialize() [function.unserialize]: Error at offset 1149 of 3181 bytes in server\system\extensions\ext.nsm_publish_plus_ext.php on line 951

Notice: Undefined index: title in server\system\extensions\ext.nsm_publish_plus_ext.php on line 969

3. Attempting to preview a new entry resulted in the following error – this consistently occurs whether or not any playa fields are present. Because this is a new entry, I’m not sure why this SQL is being created, since the entry_id is not yet set:

MySQL ERROR: Error Number: 1064 Description: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘LIMIT 1’ at line 1

Query: SELECT * FROM exp_weblog_titles WHERE entry_id = LIMIT 1

4. The last item I noticed does not appear to be an issue, but the Site_ID field is not being populated in the table used to store the draft data.

I have followed the instructions contained in the documentation for NSM Publish Plus and I believe we have everything setup correctly. Is anyone else using NSM Publish Plus 1.1.0 and experiencing these same issues?

My manager is anxious to start using this feature and I need to resolve these issues first.