Access violation in 16.2

I have a page which has a rectangular shape. In the web properties, I have some html code - an <iframe> ...

the actual code is:

<iframe src="https://services.cognitoforms.com/f/5iHK1BAdmE6T2YfMobuMKw?id=1" style="position:relative;width:1px;min-width:100%;*width:100%;" frameborder="0" scrolling="yes" seamless="seamless" height="649" width="100%"></iframe>
<script src="https://services.cognitoforms.com/scripts/embed.js"></script>

When I try and preview it, I get an access violation.

This used to work in 16.1. But it doesn't now.

Any one got an ideas on how to fix this? What I want to do is display an external form embedded in my web page. If this isn't the right way to do it, can someone let me know what it should be?

cheers

Alan

Alan, works fine for me using v16.2.

Try running v16.2 as admin, just the once.
This usually unsnags things.

Acorn

Nope - I still get an access violation.

This is a real show stopper for me.

I have just upgraded to Windows 10 v1903.

Alan

Alan, I have the same specs as you (Win 10 1903 and Xara 16.2), the form works correctly when I whack a rectangle onto the work space and paste your code into the body of the placeholder.

Works fine here too.

Wow - When I open that file and hit preview, the program just exits. No access violation - nothing.

I think my install is screwed. Time to re-install it, I think.

Alan

OK - Re-installed 16.0.0.55162 (the download version), loaded my site and the preview worked. Great.

Did the update to 16.2. It told me the previous file was not saved properly. So, I found it your test file (above), loaded that, worked fine. Loaded up my file - access violation on preview.

So, I deleted the page and copied Egg's rectangle into a previously created page of mine - and that preview worked.

I'm not over happy with what's going on, but at least I can move forward.

Alan

Mine is doing the same thing, but don't have a specific item causing other than the latest update yesterday. The last time I opened, and published this site, it worked fine. If I open it in 15, which thank God I left installed, it works, and publishes fine, but not update 16.2.

Yes, that is what mine was doing.

Alan

Edmiston, this is a strange error if it opens fine in 15. Perhaps it would help if you could send the file to Rob so the devs could have a look?

I'm getting it again. I added another rectangle, added in "<iframe src="https://teamup.com/kssit6opy1j76uyaeh" frameborder="0" width="100%" height="700"></iframe>", saved it. Got access violation on preview.

So, I then deleted that, copied the pink rectangle from the alan_sh.xar file above, replaced the code with the above. Saved the file. This time, it worked for longer and then just closed off the program.

Sorry - but this is not usable. What do we need to do to get it fixed - or how can I go back to 16.1.1?

Alan

Update - it appears to publish OK, it just won't preview. At least, when I restarted the program, and published, it worked OK. I haven't tried changing anything yet.

Alan

Hi Guys have also updated to 16.2 and just updated a web site but cannot for some reason upload it to load with filezilla. Keep getting access violation messages. Have run as administrator but no change. Tried another site which I updated before upgrade and instead of getting access violation the whole programme closed down without warning. Also closed google down with my emails open???? Reset the programme which close down Xara and it saved and exported the html where they should be.

Original site still returning access violation but noticed that when the preparing to export....export slider at the bottom was working it suddenly came up with a note regarding jpg but was on screen too quickly to read. Never seen that before.
Bug in 16.2? Is the only solution to revert back to 16 or 15. If so why are we paying for updates?

Ken

Hi just tried to run the whole site preview and get another access violation message.

Come on Xara!

It's been working fine in 16 also until now, and I didn't change anything. How would I send the file to Rob? Well, here it is unless you want me to send via another method.... Attachment 124381

Quote:

---

Originally Posted by mentorman

Hi Guys have also updated to 16.2 and just updated a web site but cannot for some reason upload it to load with filezilla. Keep getting access violation messages. Have run as administrator but no change. Tried another site which I updated before upgrade and instead of getting access violation the whole programme closed down without warning. Also closed google down with my emails open???? Reset the programme which close down Xara and it saved and exported the html where they should be.

Original site still returning access violation but noticed that when the preparing to export....export slider at the bottom was working it suddenly came up with a note regarding jpg but was on screen too quickly to read. Never seen that before.
Bug in 16.2? Is the only solution to revert back to 16 or 15. If so why are we paying for updates?

Ken

---

Ken,
You are seeing what I am too. This needs fixing

Alan

Interestingly, I also have Xara WD on my laptop. Same version and the same Windows 10 version. I open the same file (it's on a drive that's synced with my PC) and I do NOT get an access violation when I preview the same page.

I'm not sure what's going on here.

Alan

I've also had an Access Violation when trying to publish my website. No idea what's causing it except for the update. This is not good enough Xara!

Moved thread to Dear Xara.

Quote:

---

Originally Posted by gwpriester

Moved thread to Dear Xara.

---

Thanks Gary, could you also nudge Xara for us?

Acorn

I'll try.

I don't know if anyone got the file I uploaded (by request) as nobody has acknowledged my uploading it, or the receipt thereof. Here we go again. The Xara file that I'm having trouble with in 16.2.

Quote:

---

Originally Posted by edmiston99

I don't know if anyone got the file I uploaded (by request) as nobody has acknowledged my uploading it, or the receipt thereof. Here we go again. The Xara file that I'm having trouble with in 16.2.

---

Just to confirm, I do get the serious error access violation in v16.2 but not v15.1.

It occurs in Preview whole website but only Preview of the index page.
i therefore chopped ot sections until it worked.

The failing is the Placeholder with WOWSlider code for the testimonial. You have grouped other objects with is Placholder.
i simply ungrouped and all seemed to work.

Hope this helps,
Acorn


Acorn

Hi guys,

Sorry looks like smartshape placeholders are broken, we've fixed it and preparing a patch along with some other fixes for bugs that have been reported.

To fix this in the short term, create a rectangle using the quick-shape tool (the rectangle tool on the left hand side by default), and then right-click > Web Properties > Placeholder and paste your code there.

Please also remember your mobile variants if it is still AVing afterwards.

Quick way of telling if your shape is a smartshape or not - select the object and see if it has the old black handles or the new blue handles (you need to have show selection bounds on your toolbar deselected as well):

Attachment 124406

Thanks
Rob

Rob,

Thanks for the update. Any idea when the patch will be released?

Alan

I don't have an ETA at the moment unfortunately. If I was to make a guess, maybe a week or two? Depending on what gets reported and what needs fixing..

Thanks
Rob

Been through every page on the website and no smart shapes present Stil giving access violation warnings. Any other suggestions to cure before patches issued (whenever)

Ken

OK - thanks.

I can live with your workaround for now.

Alan

If it's still occuring, PM me your file and I'll take a look into it

Which file do you want Rob?

Ken

The .web/.xar project file should be fine. You can find this by going to File > Save as

Quote:

---

Originally Posted by Acorn

Just to confirm, I do get the serious error access violation in v16.2 but not v15.1.

It occurs in Preview whole website but only Preview of the index page.
i therefore chopped ot sections until it worked.

The failing is the Placeholder with WOWSlider code for the testimonial. You have grouped other objects with is Placholder.
i simply ungrouped and all seemed to work.

Hope this helps,
Acorn


Acorn

---

It super that you found it. I just don't understand why they'd release an update, that suddenly renders non-functional, aspects of how many thousands of already existing sites, and then put long time, faithful Xara users through that exercise in detective work. The grouped placeholder worked fine in 15, and even in earlier versions of 16. Why now make it not work? This is not the first time that there was an update that suddenly rendered dozens of my websites either visually incorrect, or unpublishable. Case in point, the "image" tab "One image for whole group" option. Suddenly dozens of my websites with transparent elements were no longer transparent. I had to go through, and "group", and turn on the "one image" option on quite a few of my already active websites. I can't help wondering how many of my other sites I'm going to run into this on with on my next site update. I'm sure you can understand the frustration.

Incidentally, thank you for tracking that down for me. I ungrouped, and sure enough, it published without incident. I, of course, had to re-insert the wowslider code into something, but it's working.

Quote:

---

Originally Posted by edmiston99

It super that you found it. I just don't understand why they'd release an update, that suddenly renders non-functional, aspects of how many thousands of already existing sites, and then put long time, faithful Xara users through that exercise in detective work. The grouped placeholder worked fine in 15, and even in earlier versions of 16. Why now make it not work? This is not the first time that there was an update that suddenly rendered dozens of my websites either visually incorrect, or unpublishable. Case in point, the "image" tab "One image for whole group" option. Suddenly dozens of my websites with transparent elements were no longer transparent. I had to go through, and "group", and turn on the "one image" option on quite a few of my already active websites. I can't help wondering how many of my other sites I'm going to run into this on with on my next site update. I'm sure you can understand the frustration.

Incidentally, thank you for tracking that down for me. I ungrouped, and sure enough, it published without incident. I, of course, had to re-insert the wowslider code into something, but it's working.

---

I agreed it is frustrating.

At present I have sites built in v12.8 that I dare not update through v15.1, v16.0, v16.2 or v16.2 as I too don't know what will break. I have all my major versions still loaded.
I do not know of any other application with this millstone; I updated Pinegrow, the three Affinities, Adobe and Bootstrap Studio all around the same time without incident or serious regression testing. It is two update payments so far with no tangible benefit.

Acorn

Thanks Rob removal of the small bit of code(an original work round many years ago to centre pictures) has done the trick. Acorn gave me some code to replace it as there were problems with captions on photos which were attributed to this but also to the fact that photos with shadows will not accept captions. This was a site produced back in 2015 so overlooked them

Thanks for your time

Ken

Hi Rob
Is there any update on the patch release date?

It should be released if not today then Monday or Tuesday. We're just waiting on the patches from Magix, then I'll run through and make sure they work then released.

Thanks
Rob

Quote:

---

Originally Posted by Rob-Xar

It should be released if not today then Monday or Tuesday. We're just waiting on the patches from Magix, then I'll run through and make sure they work then released.
Thanks Rob

---

Rob, it's "or Tuesday". Any news of the release?

Acorn

Quote:

---

Originally Posted by Acorn

Rob, it's "or Tuesday". Any news of the release?

Acorn

---

Apologies I've just come back from a week off.

Everything is fine on our end, waiting on Magix testing team who are apparently backed up with testing a Vegas product I think :( I'll chase them up.