[Vtigercrm-developers] Vtiger 6.0 RC - Extensions Porting Review

[Prasad]

Jonathan,

Result : Instead to have FIELD_1 and FIELD_2 in BLOCK_B, there are 2 blocks
> (FIELD_1 in BLOCK_A and FIELD_2 in BLOCK_B).
> Then, blocks sequences are not respected.


Module update is targeted to be constructive (in many cases)- meaning the
existing configuration will be persevered like ... fields etc. Due to this
BlockA with FieldA will not be dropped. Since Blocks are primarily
identified by label BlockB will be created as it is missing.

You can use vtlib_handler to adjust the destructive actions (like dropping
the field) and handle the implications. But user can customize the field
between blocks easily with Layout Editor.

Moreover, as I said in a previous email, "Filter All" fields are not
> updated.


http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/7878 - we will review post
6.0

Regards,
Prasad

*Connect with us on: *Twitter <http://twitter.com/vtigercrm> *I*
Facebook<http://www.facebook.com/pages/vtiger/226866697333578?sk=wall>
 *I* Blog <https://blogs.vtiger.com/>* I*
Wiki<http://wiki.vtiger.com/index.php/Main_Page>
 *I *Forums  <https://discussions.vtiger.com>*I*
Website<https://www.vtiger.com/>


On Sat, Dec 28, 2013 at 2:08 AM, Jonathan Sardo <sardoj at gmail.com> wrote:

> Prasad,
>
> I found some road-blockers, during modules update.
> All functions are not implemented in PackageUpdate.php and there are
> problems with filters, events et blocks.
>
> For exemple :
> 1)
> - Create a block called BLOCK_A
> - Add a field FIELD_1 to BLOCK_A
> - Install the module
>
> 2)
> - Rename BLOCK_A and call it BLOCK_B
> - Add a field FIELD_2 to BLOCK_B
> - Update the module
>
> Result : Instead to have FIELD_1 and FIELD_2 in BLOCK_B, there are 2
> blocks (FIELD_1 in BLOCK_A and FIELD_2 in BLOCK_B).
> Then, blocks sequences are not respected.
>
> Moreover, as I said in a previous email, "Filter All" fields are not
> updated.
>
>  Regards,
>
> Jonathan SARDO
> [image: Images intégrées 5]
>
>
> 2013/12/27 Prasad <prasad at vtiger.com>
>
>>  Stefan,
>>
>> Vtiger 6 listview provides meta information as part of data-* attributes
>> on the HTML elements.
>>
>> The default layout listview - <tr> element records id in the attribute
>> (data-id) and
>> each <td> has information about field-name (fixed<http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/7880#comment:1>
>> )
>>
>> Regards,
>> Prasad
>>
>>
>> *Connect with us on: *Twitter <http://twitter.com/vtigercrm> *I* Facebook<http://www.facebook.com/pages/vtiger/226866697333578?sk=wall>
>>  *I* Blog <https://blogs.vtiger.com/>* I* Wiki<http://wiki.vtiger.com/index.php/Main_Page>
>>  *I *Forums  <https://discussions.vtiger.com>*I* Website<https://www.vtiger.com/>
>>
>>
>> On Fri, Dec 27, 2013 at 5:32 PM, Stefan Warnat <ich at stefanwarnat.de>wrote:
>>
>>> Hy,
>>>
>>> Yes. I found one real blocker, I couldn't solve via JavaScript to save
>>> performance.
>>>
>>> The DetailView was improved heavily to increase extending features.
>>> (After the moment I understand the new Widget System with Sidebars)
>>>
>>> But the ListView is missing some features I used to highlight rows.
>>> There are no more attributes *vtfieldname* and *vtrecordid* in ListView.
>>>
>>> But probably they are not needed if there will be a way to modify the
>>> behavior of the "List" View in Accounts module from my Extension module.
>>> The documentation don't say anything about this. But perfect will be a
>>> function to interfere in the Template Parsing or Handling of a view in
>>> selected module. But I don't have any Idea, how this could be done.
>>>
>>> I fear a similar ListView handling, like I do in 5.40 is not possible in
>>> 6.0 in this easy way.
>>> I will need to migrate my increased EventHandler (
>>> https://github.com/swarnat/vtigerCRM-EventHandler) to 6.0 to allow
>>> extended List modifications. (Probably this will be a way to handle this in
>>> Core, like Wordpress does)
>>> This don't impact the performance and allows very much new extensions.
>>>
>>> I think most developers need only a way to insert or search/replace
>>> parts of the output.
>>>
>>> But: 6.0 is a great software!
>>>
>>> Stefan
>>>
>>>
>>> On Fri, Dec 27, 2013 at 11:25 AM, Prasad <prasad at vtiger.com> wrote:
>>>
>>>> I hope you are having good Christmas time!
>>>>
>>>> We are curious to know if you are hitting any road-blockers, while
>>>> porting extensions
>>>> to Vtiger 6 from earlier versions or create new ones.
>>>>
>>>> Please refer to updated documentation at:
>>>> http://community.vtiger.com/help
>>>>
>>>> Keep us posted with your journey.
>>>>
>>>> Regards,
>>>> Prasad
>>>>
>>>> _______________________________________________
>>>> http://www.vtiger.com/
>>>>
>>>
>>>
>>> _______________________________________________
>>> http://www.vtiger.com/
>>>
>>
>>
>> _______________________________________________
>> http://www.vtiger.com/
>>
>
>
> _______________________________________________
> http://www.vtiger.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20131228/e358a72f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 4223 bytes
Desc: not available
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20131228/e358a72f/attachment.png>