Don't touch "Duplicate Field Configuration" - Actinic can't fix it for 2 releases!
There is a bug within V9.0.1 that seems to relate to duplicate products and the Extended Info file name.
We have a mature database with hundreds of duplicate items that has worked fine for many releases including our current 9.0.1 release.
Suddenly when selecting "Publish to web" we started getting the following error:
"A page named 'C:\Actinic\V9\Site1\SiteHTML\' has already been generated for the extended info page 'PRODUCT 1'. The same page name is used for the extended info page 'PRODUCT 2' and therefore the previously created page will be overwritten."
for just about every duplicate product (even the ones without extended inf pages!).
Now I don't remember doing it, but I suspect at some point I had a look at the "Duplicate Field Configuration" settings which I guess have changed something with the database.
Looking through the threads it seems others have had similar problems in the past, but usually with just a few products, but we have hundreds.
Actinic Support are a complete waste of space
, I tried calling several times just went to an answering machine (which from past experience takes a day to get listened to), so I emailed them. Despite several emails and finally getting through on the phone, it has taken them nearly 3 weeks to tell me it is a bug in the software and that it can't be fixed for the next release, but should be for the one after!!!
They also failed to request a workaround from development despite being asked (though I would have thought it a natural thing to do)
When we did get a workaround request answered, the only solution they suggested was an SQL query to reset all our duplicate "Short Descriptions" to match the parent product - which is neither use nor ornament to us as we need different short descriptions for the duplicates.
I wonder just why we pay for support!
Anyway, little rant over, I can't afford to spend an hour a day hitting the "Y" key on the keyboard for the next however many months waiting for a fix, so I thought I would see if the community had any suggestions.
Perhaps an SQL query to give a unique Extended Info page name to each duplicate in the database.
Any suggestions more than welcome....
We have a mature database with hundreds of duplicate items that has worked fine for many releases including our current 9.0.1 release.
Suddenly when selecting "Publish to web" we started getting the following error:
"A page named 'C:\Actinic\V9\Site1\SiteHTML\' has already been generated for the extended info page 'PRODUCT 1'. The same page name is used for the extended info page 'PRODUCT 2' and therefore the previously created page will be overwritten."
for just about every duplicate product (even the ones without extended inf pages!).
Now I don't remember doing it, but I suspect at some point I had a look at the "Duplicate Field Configuration" settings which I guess have changed something with the database.
Looking through the threads it seems others have had similar problems in the past, but usually with just a few products, but we have hundreds.
Actinic Support are a complete waste of space
, I tried calling several times just went to an answering machine (which from past experience takes a day to get listened to), so I emailed them. Despite several emails and finally getting through on the phone, it has taken them nearly 3 weeks to tell me it is a bug in the software and that it can't be fixed for the next release, but should be for the one after!!!They also failed to request a workaround from development despite being asked (though I would have thought it a natural thing to do)
When we did get a workaround request answered, the only solution they suggested was an SQL query to reset all our duplicate "Short Descriptions" to match the parent product - which is neither use nor ornament to us as we need different short descriptions for the duplicates.
I wonder just why we pay for support!
Anyway, little rant over, I can't afford to spend an hour a day hitting the "Y" key on the keyboard for the next however many months waiting for a fix, so I thought I would see if the community had any suggestions.
Perhaps an SQL query to give a unique Extended Info page name to each duplicate in the database.
Any suggestions more than welcome....
Comment