Loss of Drag and Drop

[Confused Sally]

Hi,
I am just playing with v11, how are you finding the loss of drag and drop. I would always import from EPOS without a heirachy, hide all the products and then drag and drop to different sections. The delivery of the import from EPOS meant that products did not appear in any order in the tree and so i would drag them into groups before transferring to a section.often we make duplicates and they sit in different sections eg a Fabric may be in 'New', 'Red', 'Floral' and ' Tiny prints' However in v11 once an item has a duplicate you cannot drag it anywhere, you cannot cut and paste it, so it has to stay where youfirst put it. Anyone found a way round this?

[Duncan Rounding]

I can't replicate this - it works for me in 11.0.1. I import products into one single section then drag them to their final location. Having duplicates or not also seems to be fine.

[Confused Sally]

Hi I have mentioned it to support and received this reply

'It appears exactly the same thing happens for me in v11, when I try to cut a section which has a product which has been duplicated in it. I am afraid this appears to be in place to protect Actinic from problems, we can’t work around that'

so is there something you know that i don't?

[Duncan Rounding]

I've just been playing around with dragging and dropping products, duplicates and sections and it all seems to work for me. There must be something that I'm not trying I presume then.

[Jan]

Is this a feature of multiuser perhaps? The lack or drag and drop.

Regards,

[I-CC]

I could be wrong - not tested - but do recall similar, that this is when the EPOS link connection is in operation, thus it gets prevented

[Confused Sally]

Hi All,
have restarted V.11 following a test publish and this morning the drag and drop seems to be working fine, so not sure what was causing it. Have tried with both EPOS link on and off and it worked!

[I-CC]

See if the lock kicks back in once you have transfered data between the epos and EC.

[chrisframe]

Very slow Drag and Drop

Dont know if its the same problem; but I had a similar issue with Drag and drop taking 2 to 3 mins each time. Turned out to be a change of "primary key" in the product table away from "Product Reference" . I also have 5 extra fields ID, ID1, ID2, ID3 and ID4, pehaps someone may know where these came from?. Hope this helps it took nearly 6 months for me to find out.

[Confused Sally]

Have been told bysupport the following

'Our developer has been looking into whyActinic was hanging upon opening. This is due to a known bug in Actinic called “actinichangs on initialising site objects following drag n drop” (Bug reference:AC11-2433). As this is a bug, our developers will be working towards fixing itfor a future release of the software.

The only workarounds we can offer for thisbug are as follows:

Avoid dragging and dropping products and sectionsin Actinic. If you do drag and drop products / sections, you run the risk ofActinic taking a very long time to open afterwards.'

However despite avoiding dragging and dropping, but we do a lot of cutting, copying and pasting, our Actinic v11 just hangs on 'initialising site objects' and then becoes impossible to open, advised by support to wait for 2 hours at least for it to open - anyone else found 2 hours does the trick?

[chris ashdown]

Its a feature of Business plus and always has been that if more than one person is using a site then the drag and drop is not working, but all works ok when you only have one person on site

[Confused Sally]

Loss of Drag and Drop, problems with cut and paste

Just an update, Chris is correct that drag and drop works when only one user is logged in on Business plus. However we are finding that we get occaisional crashes and Actinic takes forever to open (yesterday it was 4 hours) if we have cut and pasted a few products, I have been advised by support to avoid dragging, dropping and cutting, pasteing. This makes organising the site and working in the way we used to work (importing then reshuffling) very difficult if nigh on impossible. A fix for this bug is planned for the next release, hopefully support will test it on my system.