Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Error on Publisher entry save

Status Resolved
Add-on / Version Publisher Lite 2.5.0
Severity
EE Version 3.5.4

KeesTM

Jun 19, 2017

Description:
I get an error after I save an entry with Publisher. I’ve installed Publisher Lite 2.5.0 and Bloqs 3.1.2 n ExpressioEngine 3.5.4

Detailed steps to reproduce the issue:
1. Open an entry
2. Change text in a Bloq
3. Save entry

SQLSTATE[42000]: Syntax error or access violation: 1064 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 ‘)’ at line 3:
SELECT `blockdefinition_id` FROM (`exp_blocks_atomdefinition`) WHERE `id` IN ()

 

 

#1

BoldMinded (Brian)

Sorry about that. I think I ran into this myself last week. The build linked in the next comment may include the fix.

If this build does not fix the issue I’m going to need a lot more detail. E.g what atoms are defined in each block available to the entry (screenshots may help), or create a quick video so I can see the behavior happen.

#2

BoldMinded (Brian)

Comment has been marked private.

#3

Est Digital

Thank you for your quick reply! I’ve added details so you can login the backed of our Acceptance environment. Actually, the machine has trouble getting past Publisher’s installation to start with: After a couple of page reloads it seems to be installed, but then the error i sent you appears when I try to save an existing entry in the channel “Dot Detailpagina”. Hopefully you can point me in the right direction?

#4

BoldMinded (Brian)

“Actually, the machine has trouble getting past Publisher’s installation to start with: After a couple of page reloads it seems to be installed” - Did you get an error message? What makes you believe it had trouble getting past the installation?

Also, have you tried creating a clean EE environment with only Publisher and Bloqs installed? Does it happen when adding a specific block to an entry? Or does it happen when you add any block to an entry? If so what atoms are added to the block?

I don’t login to sites or servers unless its a last resort. Please provide more information, preferably a video of the issue occurring, and answering the preceding questions.

#5

BoldMinded (Brian)

Does the error occur only in the “Dot Detailpagina” channel? If so, what is unique about that channel compared to other channels? What custom fields does it have?

#6

BoldMinded (Brian)

I usually don’t do this but I logged into your CP anyway. I saved 2 entries in the “Dot Detailpagina” channel and there were no errors. At this point I need to ask that you record a video of the error so I can see it. Also provide an the title or entry_id of the entry that the error is happening on so I can also login and look at it if I need to.

#7

Est Digital

Sorry, it took so long for my to reply: I’ve been out of the office for the last couple of days…

I wanted to create a video this morning, but our Acceptation environment produced a different kind of error from the one I saw on our Development environment (MAMP) when I wanted to install Publisher: SQLSTATE[08S01]: Communication link failure: 1153 Got a packet bigger than ‘max_allowed_packet’ bytes So I contacted our server guy and let him adjust it to 16mb.

After that, the url_helper addon had to be updated, because it was asking for publisher_lib, which doesn’t exist in the latest version. After disabling Gzip output in the master config, I’m now in a situation where it’s almost working. The only error which seems to be standing in the way is: preg_match_all(): Compilation failed: regular expression is too large at offset 257095 ee/legacy/libraries/Template.php, line 361

Am I still doing something wrong?

#8

Est Digital

I found this fix to get rid of the errors, but it feels like I’m hacking the EE core.. https://expressionengine.com/forums/topic/249930/global_vars-and-regular-expression-is-too-large-error

#9

BoldMinded (Brian)

If you’re using 3.5.4, then you are hacking EE core. That fix should be included in the 3.5.7 version of EE so you don’t have to hack it.

So that was the only remaining issue?

#10

Est Digital

Yes, that was it. Thank you for your help!

Login to reply