+1-888-365-2779
Try Now
More in this section

Forums / Upcoming Features / Sitefinity 6.2 Internal Build Available for Download

Sitefinity 6.2 Internal Build Available for Download

34 posts, 3 answered
  1. Kali
    Kali avatar
    158 posts
    Registered:
    25 Feb 2009
    25 Sep 2013 in reply to Jochem Bökkers
    Link to this post
    Hi Jochem,
    The last problem with  nothing selectable/editable in the top bar was fixed and will be included in the beta later this week. Thanks for the report!

    -Kalina
  2. Jochem Bökkers
    Jochem Bökkers avatar
    787 posts
    Registered:
    13 Aug 2007
    25 Sep 2013
    Link to this post
    Hi Kali,

    The inline-editing calls several files with the extension .html which will conflict with any rewrite rules that might exist to preserve old serp links.

  3. Kali
    Kali avatar
    158 posts
    Registered:
    25 Feb 2009
    26 Sep 2013
    Link to this post
    Hi Jochem,

    Thank you for pointing us to this potential issue!
    We will change .html extensions to .sfhtml in order to prevent any conflicts with rewrite rules.
    We can continue the discussion in the Sitefinity 6.2 Beta forum, announced today.

    Thanks again,
    Kalina
  4. Kali
    Kali avatar
    158 posts
    Registered:
    25 Feb 2009
    26 Sep 2013 in reply to Kali
    Link to this post

    Hi Steve, my responses are with ### below:

    - Rename the script functions\global vars to something less generic than "openUpdateWindow" and $popup?...conflicts and such.
    >>>Our functions are wrapped in requirejs modules. Which functions/global vars do you mean?
    *** In edit more there's a function inserted into the page called "openUpdateWindow" with kendo window code in it, and a global variable called $popup in the same method.  The names are just too crazy generic, especially openUpdateWindow. 
    ### Those functions are not defined from us and in debug mode we cannot see them defined. Can you specify in which files you found them defined?

    >>> Submitted request to Kendo team. They explained that when you change the styles using block tags, the change is applied to the whole block/paragraph. If you apply styles using inline tags, these are be applied to the selection of text only. The workaround in this case is to hit enter after the text, and apply
    style to it after that.  Please let me know if that makes sense.
    *** Makes sense, but you're (well I guess us developers) gonna have to explain that to everyone having that experience.  IMO if I'm selecting some text I only want that text wrapped.
    ### Can you check the demo of RadEditor, and let me know if this is how this should work?

    - Can we get the ability to configure if the "stauts" is shown by default?
    >>> Status indicator will be displayed for Drafts and Locked items only . This will give indicator to the user that he is working with content which is not published on the site or that content is
    locked. Switching off/on of statuses is there for test purposes only. What do you expect to be the default state?
    *** I would want to see them by default, right now it's hard to know when I'm in edit mode
    ### This was reworked in the Beta build. Please review and let me know if this is more usable now.

    - Might be conflicting styling, but the publish\draft buttons have no margin below them (see attached)
    >>> We couldn’t reproduce this problem. Can you please submit a project which we can review?
    **** JUST saw this on the partner webinar as well, they were using quantum (attached)
    ###This issues should  be fixed in the Beta build.

    *** Error messages are nice, but I'm more concerned that I was able to take a page that was editable into a state where every ajax call crashed :)
    ###This should be fixed in the Beta build.

    I would also like to thank you for the useful comments and suggestions. They are very helpful! I suggest we continue the discussion to the Beta build thread.

    Best,
    Kalina
34 posts, 3 answered
1 2