R183 System Update - Scheduled to go live January 22nd, 2013

Hi Jackson,

Thanks for the details but you listed it as "May".

Regarding #2801224 and the new parameters for product list sorting, will this be documented and the Dreamweaver BC panel updated?  In general, whenever new tags, modules, and paramenters are available they should be documented in the applicable Quick Reference KnowledgeBase and the Dreamweaver and Admin panels updated to reflect it.  This hasn't always been the case and there is nothing more frustrating than turning down BC clients or providing reduced or hacked functionality when what you need BC to do is actually already doable but just not documented.

Great release though and keep it up!

Fixed, Easy to run off one of the old posts to do these so that can happen.

In terms of documentaiton - I would hope so but really do not expect it to be up to scratch any time soon if at all, lol. They say they working on it, and let them know when you find issues with it all, but they have a lot on plate to first "get it" (understand what to put down and why and processes to ensure they are implemented) and then apply it to documentation

One of the main reasons jQuery became so popular early on is not that it was so much better than rival frameworks, but because it's documentation was so much better.  Organized, easy to understand, great code examples, continuously updated, etc. 

If Business Catalyst wants new people to adopt this platform, much better documentation would go a long way towards that.  The panels in Dreamweaver and the Admin in particular always need to be updated.  It doesn't make sense to offer something like that but it not actually reflect what is possible or have you using functionality that is deprecated. 

Documentation is extremely important.

"{tag_tellafriend} and {tag_tellafriendurl} will no longer be available for use in email campaigns."

Can we still use it though, if you hand code it?

I would disagree with that, For a long time even using jQuery the mootools documentation was a lot better.

jQUery did not have the animations but it had everything else very well. Then they improved the animations and more, the people involved also increased its popularity and those and the improvements they still do today and the weight of it (moreover the lack of) has lead it to be the one to use.

But you are also not wrong in the thoughts of the bc docs. That is why I am building my own KB (free to use) for everyone.

Great stuff Jackson,

Is there a particular reason why the Tell a Friend Tag is getting removed from Email Campaigns? is it due to Spam Laws?

The reason I'm asking as there are some clients that provide offerings or discounts to people refering their friends and it is quiet effective "Marketing Wise".

Issues:

1. The ecommerce Stock attribute beta is live with the bugs reported in beta. Including the main one where if you have products with stock attributes, despite them rendering in the export file you can never import products back into the system because of stock sku features. Deleting all products allows you to upload with all sku information as a work around but on some uploads stocks are reset to 0.

2. Intermintant permission issues creating folders that have same name as web apps.

3. Can not make folders in BC editor (under develop) that are existing web apps

4. If you move a pre existing page via FTP into a new created web app folder and rename it to index.html It will not work. In the admin it has no file extension so you have to add it there.

5. Just had it confirmed by live chat support who replicated it on a demo site. Securezone update details form with custom CRM fields.

CRM fields will render current data but will not update the custom CRM fields in the crm on submission of the form.

Has anyone noticed that some fixes from the last release have been broken again after this release? i.e the Title on Customer Details started showing the Value Number of the Field rather than the Title itself again, with that, I'm sure there are other fixes that have been broken too. Maybe a revision to the last release should be performed again.

This bug correction has been indeed reverted soon after the R182 release because some sites were using the IDs that were outputted by the module as input source for JavaScript scripts.

We will release a different implementation of the fix that will imply:

• Addin an output parameter to the module
• Adding two values for this new parameter: id or value
• Default to ID to not break existing websites
• Have partners that need value update their pages so that the module will consider the value {mdodule_title, value}

Best regards,

Cristinel

Thanks Cristinel,

But some kind of notification to let us know about this would've been nice. I think it's fair that you respond to enquiries regarding an issue faster than expected, but it is also fair to let the rest of us know about it. So far we're living with favoring requests over others, but I don't think many of us would live with even ignoring everyone else.

I know this is a slight issue, but can cause a bit of trouble if you have many sites to manage during very busy times to stop everything else and go back to fix all sites again, and also how many of similar situations happened that we don't know of?

Anyway, I don't expect you to respond to this, but a better communication will be appreciated - specially now that you guys are entering a phase with major updates and changes.

Thanks.

Hello,

We usually include this type of change in a known issues document that is issued (when the case) right after a release. Sadly, it seems that this item in particular has not been included in the R182 known issues document and we'll fix that.

Kind regards,

Cristinel