Section Specific List of Brands

[leehack]

I think its the amount of sections on this one more than anything, its huge. Its beyond what actinic can realistically handle in all honesty, at least in what you'd call a timely fashion. To put it into perspective i have a 5,000 product site, with probably 4,500 images and that snapshot is only 28MB. It is also coded in the worst way i could possibly imagine and has more nested tables than your local IKEA.

I don't think clean coding is the key personally on performance, it's all about the number of sections IMO.

[jont]

Originally Posted by leehack

I don't think clean coding is the key personally on performance, it's all about the number of sections IMO.

It is going to be due to lots of factors in the actinic melting pot. The site I mentioned also has a shed load of sections and subsections (and about 60 brochure pages) ... saying that ... I also do away with the vanilla navigation.. some of the supplied section navigation code is very heavy duty (as Norman as pointed out on a current post) which inevitably requires a lot of processing time to compile.

[leehack]

Timewise, I think actinic is far better at producing one page sizing 300k, than 10 pages of 20k. As i am sure you know, Norm's dynamic menus are pretty much as clean as you can get them, when it was added to this site, 180kb was added to each page, now that is what you call section hungry lol. You could lose 300 sections on this site and never know.

[brant@on-one]

Hmmm... and there's no 3rd party way of doing stock control by passing the upload? (Sorry - still getting to grips with the architecture)...

We've got a fun project on as next thing I need to plan is an export from Actinic to Cognito Moneyworks - our accounts package of choice (rather than Sage or whatever)...

Has anyone done a link direct into some stock qtys info (it must be held somewhere) rather than reloading the site?

[Jan]

We've got a fun project on as next thing I need to plan is an export from Actinic to Cognito Moneyworks - our accounts package of choice (rather than Sage or whatever)...

This plugin might help you with that - it allows you to export orders from Actinic into a csv file.

http://www.mole-end.biz/acatalog/One...ssing.html#aQO

Regards,

[wfl]

Well if we are very lucky (and perhaps CD will confirm or deny) 8.5.2 will have the ability to turn the review on or off.

After all it might be OK on occasions but it is unnecessary for regular uploads.

[brant@on-one]

And how far off it 8.5.2?

[wfl]

Depends who you ask but the latest whisper I heard is beta by the end of the month.

As the end date has grown one can only hope the number of fixes it includes have grown - and been tested

No secret but frankly I am just about ready to start working in beta (after a quick look see) - after all how much worse can it be.

If it doesn't come soon it will be overtaken by events.

[cdicken]

Hi all - this is a really good discussion. I've passed on the request about setting up different marketing campaigns etc. to the development team.

I guess the tree system is fine for smaller sites, but as soon as you get lots of problems, you just want to have a list of all products and then just a checkbox to decide what section(s) they should be in. I'll pass this on to the team.

[wfl]

That is food for thought Chris.

Extending these ideas would create a really powerful tool without making the db any more cumbersome than need be as the products would only have to exist once and not in many duplicates.

Marketing pages for ad and cpc campaigns would be ideal. I tried and failed to get some enthusiasm for this elsewhere, http://community.actinic.com/showthread.php?t=32160, but I did lodge the idea with MarkR and I still think it is worth considering. After all it is a component that already exists and could easily be reused.

As you can imagine I do like the idea of treating the product db as a single product repository and then linking the products to pages on which you want them to appear.

In effect these two approaches could be the same thing but possibly not if you want to change the product details in different sections. On the other hand if all the product data exists in the product db and all you are doing is changing the appearance then it would not affect the product db.