EE4/5 compatibility updates:

  • Publisher is EE4 and EE5 compatible, but it does not currently support the Fluid field (it's in the works).

Ticket: images failing to attach to entries

Status Resolved
Add-on / Version Bloqs 4.0.16
Severity
EE Version 5.1.2

Tim Murtaugh

Jan 03, 2019

All of a sudden (but before today’s latest EE update to 5.1.2), images selected within a blog field aren’t being saved. The selector shows up, and appears to work, but when you select an image the thumbnail doesn’t appear, and the image doesn’t show up after saving the entry.

I know there have been some recent updates to EE’s native file field — perhaps it broke something?

#1

BoldMinded (Brian)

Jan 03, 2019

No I’m not aware of any changes. Have you tried replicating it in a new environment to see if it’s a actual bug or if something is wrong with your current environment?

#2

Tim Murtaugh

Jan 03, 2019

I’ve replicated it in two environments, both before and after updating to the latest versions of the add-on, as well as before and after the very latest versions of EE.

#3

BoldMinded (Brian)

Jan 03, 2019

Ok, I’ll try to replicate it tonight and take a look.

What other addons do you have installed? Publisher?

#4

Tim Murtaugh

Jan 03, 2019

A few add-ons, but not Publisher:

Bloqs
Digi Nut Control Panel CSS & JS
Field Pack
Freeform Pro
Hop Super Pulldown
Low Reorder
Low Seg2Cat
MX GetID3
Simple Grids & Tables
Template Sync
Time Select
wCloner

#5

BoldMinded (Brian)

Jan 03, 2019

All your image data should still be there. Something changed in the new File field UI that is not removing a “hidden” class from a div, thus the field is hidden inside of Bloqs. Not sure how to fix it yet.

#6

Tim Murtaugh

Jan 03, 2019

In the inspector I noticed that the data seemed to be populating in hidden areas, but it doesn’t save. After saving the entry, the drag and drop zone is there again, and the image doesn’t show up on the front end.

#7

BoldMinded (Brian)

Jan 03, 2019

Right, if you save a field that is visually hidden on the page it isn’t in the POST data, so it’s wiping the field value clean. I’m testing a fix right now.

#8

BoldMinded (Brian)

Jan 03, 2019

Created a new issue for EL to track the issue. A new build with a fix will be in the next comment.

https://github.com/ExpressionEngine/ExpressionEngine/issues/76

#9

BoldMinded (Brian)

Jan 03, 2019

Comment has been marked private.

#10

Tim Murtaugh

Jan 04, 2019

Thanks for this — all seems well.

#11

BoldMinded (Brian)

Jan 04, 2019

Sweet smile

#12

Tim Murtaugh

Jan 08, 2019

Just FYI, I have to re-save existing entries before they will allow images to be attached,

#13

Tim Murtaugh

Jan 08, 2019

Actually, I have more to report:

It seems to only be working if the block I create is in the first position. If I create a block below the first block, the bug still occurs, and images don’t attach.

#14

BoldMinded (Brian)

Jan 08, 2019
#15

BoldMinded (Brian)

Jan 08, 2019

Yeah, this new File field re-written in React is causing problems. Don’t know long it’ll take to fix it, or how to fix it at this point in time.

#16

Tim Murtaugh

Jan 08, 2019

I don’t have the ES6 files, I presume there are EE updates on the way that I don’t have?

But I made the other changes on my staging server, and here’s what happens:

1. Add block with image field in the first position, select an image, seems to work fine.
2. Add a second block with an image field, select an image, both blocks get updated with the second selected image.

After seeing this, I went back to the production server to see what happens when you select a field in a second block (without your suggested updates):

1. Add block with image field in the first position, select an image, seems to work fine.
2. Add a second block with an image field, select an image, only the block in the first position gets updated..

#17

BoldMinded (Brian)

Jan 09, 2019

Tim, thanks for the steps to replicate. I can also replicate locally and it is due to the File field being re-written as a React component. I almost have it working in Bloqs again, but there are a couple more things to work on. I’ll try to get you a new build this week but I can’t be 100% sure. I’ll do what I can.

#18

BoldMinded (Brian)

Jan 09, 2019

Comment has been marked private.

#19

Tim Murtaugh

Jan 09, 2019

Awesome!

There’s one typo in views/editor.php on line 65: `style=“display:noneX;”`

I fixed it on my end and all seems to be working on staging, I’ll push to prod and let you know if anything comes up.

#20

Kees Internetbureau

Jan 10, 2019

Got the same problem, just subscribing for email notifitcations

#21

BoldMinded (Brian)

Jan 10, 2019

I’m going to upload the official release with the fix here in the next couple of hours.

#22

BoldMinded (Brian)

Jan 10, 2019

Fixed in the 4.0.18 release.

Login to reply

Contact

For add-on support, please use the Support section. General inquries and pre-sale questions can be sent to support@boldminded.com.