Doesn't seem to be compatible w/ concrete v8.3.1
Permalink Browser Info Environment
I was able to create a form, add the block to a page and submit, but the form doesn't appear to do anything (send the notification). When I revisited the dashboard the form disappeared and was presented w/ the Welcome to Formify message. I attempted to add additional forms w/ the same results.
Type: | Ticket |
---|---|
Status: | Archived |
Thanks Phil, surprisingly it was my browser (Chrome) once I cleared my cache I could see all the forms on the main screen.
Just a note, I'm still having issues w/ caching via Google Chrome and Firefox on the main /dashboard/formify/forms screen only. It seems the information is loaded via JavaScript and continuously gets stuck in cache. For example today I added three tests forms and deleted two of them, however the deleted forms still appear in Chrome and Firefox but not in Microsoft Edge. I've not experienced this w/ any dashboard pages in the past. Has anyone else had experienced this?
Here is a video of new forms that didn't appear on the dashboard at all until I cleared my browser cachehttps://monosnap.com/file/pCJVB8RK60A7N20pIYWhtuVoNUsakJ...
And here is a video where deleted forms still appear in the dashboard
http://take.ms/R06DS
Here is a video of new forms that didn't appear on the dashboard at all until I cleared my browser cachehttps://monosnap.com/file/pCJVB8RK60A7N20pIYWhtuVoNUsakJ...
And here is a video where deleted forms still appear in the dashboard
http://take.ms/R06DS
Hi,
Try switching off all the caching in Concrete 5 to see if that makes a difference.
Best
Phil
Try switching off all the caching in Concrete 5 to see if that makes a difference.
Best
Phil
I appreciate the reply Phil, I did try that but it doesn't make sense really I'm not sure why caching would apply to dashboard pages to begin with. I will wait to see if Justin has any input on Thursday, I've tested in multiple browsers on both Mac & PC and get the same results.
Hi,
The reason I mentioned caching was that in an earlier version of formify another user and I had a similar issue to yours and I just switched all caching on the site to ON except for css and javascript caching which I left OFF (in system and settings - Cache & Speed Settings) and then formify worked fine.
At that time Justin wrote there may be a way he could disable any sort of caching on the formify dashboard page within the package itself. I am not sure if he actually did that
Best
Phil
The reason I mentioned caching was that in an earlier version of formify another user and I had a similar issue to yours and I just switched all caching on the site to ON except for css and javascript caching which I left OFF (in system and settings - Cache & Speed Settings) and then formify worked fine.
At that time Justin wrote there may be a way he could disable any sort of caching on the formify dashboard page within the package itself. I am not sure if he actually did that
Best
Phil
Ah gotcha that does makes sense then..., I did try your suggestion since it feels like a caching issue for sure but even after disabling everything and clearing the c5 site cache I get the same results. Anyway, thanks again Phil for taking the time to reply, the one week response time from the developer is tough when you're trying to find a quick solution and a core feature doesn't work consistently while testing.
Hi,
I understand your frustration. I have been trying to replicate the error on my wampserver installation of 8.3.1 but my formify behaves perfectly regardless of which cache settings I use. So that is odd. I notice you are using php 7.0.13 can you try a different php version. Again in some earlier versions formily was sensitive to different php.
I know that unless the developer can replicate an issue it is often impossible to resolve it.
Best
Phil
I understand your frustration. I have been trying to replicate the error on my wampserver installation of 8.3.1 but my formify behaves perfectly regardless of which cache settings I use. So that is odd. I notice you are using php 7.0.13 can you try a different php version. Again in some earlier versions formily was sensitive to different php.
I know that unless the developer can replicate an issue it is often impossible to resolve it.
Best
Phil
I'd prefer not to adjust my PHP settings to cater to one App, I never like to do that. If Formify doesn't work properly in a live environment using PHP7.1 then we can't use it, no big deal.
It's also not unusual for my team to discover issues, we build a lot of c5 sites and were first to report many core issues in v8 when that first came out. I'm sure someone else will bump into this eventually so we'll see what happens. I'll keep on eye on the ongoing updates and try another time, from what I've seen so far he's made some nice improvements to the UI and it looks promising.
It's also not unusual for my team to discover issues, we build a lot of c5 sites and were first to report many core issues in v8 when that first came out. I'm sure someone else will bump into this eventually so we'll see what happens. I'll keep on eye on the ongoing updates and try another time, from what I've seen so far he's made some nice improvements to the UI and it looks promising.
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.
To re-open this issue, reply to this message.
To re-open this issue, reply to this message.
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.
To re-open this issue, reply to this message.
To re-open this issue, reply to this message.
I just ran some formify 3 tests with 8.3.1 on a wampserver with no issues. Using php 5.6 and 7.0.23 and 7.1.9. I don't have a live 8.3.1 site with formify 3 but I don't see any obvious reason for any kind of problem.
The only environment difference I have compared to yours is
Full Page Caching - Off
Best
Phil