7 Responses

  1. Patty
    Patty August 11, 2016 at 15:03 | | Reply

    I went and took a look at the theme website and company website. The theme looks interesting, but it puts me off when an “About” page says nothing about where the company is located. I know they probably have lots of people working remotely, but surely they have main offices in some country or other? When they refuse to say, it just seems like a bad sign.

    Also bugs me when a theme company misspells “WordPress” front-and-center on their site. I know, it’s not the end of the world, but it just erodes my confidence in them a bit!

    1. mark.zahra
      mark.zahra August 15, 2016 at 12:52 | | Reply

      Hi Patty, I understand your issue with WordPress being misspelt, I can’t stand that either, but what’s the issue with not having a single physical location? Many companies and teams nowadays work remotely without a physical office as a central point of reference. As long as they offer support and it’s quality support, there shouldn’t be any problems 🙂

  2. Vladimir
    Vladimir August 22, 2016 at 13:23 | | Reply

    Guys from Kallayas are paying for posts now? I don’t want to sound as a troll, but I had a really nasty experience with this theme some time ago when I had to update it and it broke a client’s website although we were using a child theme. Styles happened to be broken too, as some of the classes in the markup were changed.

    It could be the case that I came to project at the wrong time, but rolling out a new version with rewriting everything in the theme, without providing backwards compatibility for child-themes developed before ain’t cool.

    1. mark.zahra
      mark.zahra August 23, 2016 at 02:23 | | Reply

      Hi Vladimir, did you contact Kallyas about this? What was their feedback?

      Can you please explain what you meant by backwards-compatibility with child themes?

      1. Vladimir
        Vladimir August 23, 2016 at 05:08 | | Reply

        Sadly I can’t dig into the communication that was lead about an year ago (when the major new 4.0 was released). I am not entirely sure if support of Kallayas was contacted, but that wouldn’t help much, as the problems were clear and there was no point in asking for directions at the time.

        By backwards compatibility I meant always considering child themes, developed for older version of your theme. Function, constants, global variables, classes and so on should not be renamed or at least some stubs should be left in order to prevent those child-themes from breaking. Same should be done for classes and ids. I can’t tell all of these were broken rules in Kallayas upgrade to v.4.0, but I do recall having some bad time after the upgrade, coping with such issues.

        Most probably newer users won’t have the same problem, as long as there are no major rewrites. Same applies for non-developer users, who are not even bothering with child themes and overwriting templates. Nevertheless, I felt like I should share my experience.

        1. mark.zahra
          mark.zahra August 24, 2016 at 05:14 | | Reply

          Thanks for sharing Vladimir.

          Indeed, I don’t see this being an issue now, and yes, you should always work with a child theme rather than making changes to the main theme. If you don’t create a child theme you will always have trouble with updates.

          As much as I understand your point and agree with you, from experience, I know that certain changes and updates could cause some incompatibilities, but they would also be required for the improvement of the theme or plugin.

          1. Vladimir
            Vladimir August 25, 2016 at 12:45 | | Reply

            Yet another thing that I just remembered now (as my client complained of the page load speed) – there are elements from the builder that don’t care what size of image they are displaying and on what screen, so we end up with about 10Mbs of images from the Portfolio Archive, without control over the sizes of the images that will be shown as thumbnails. Same issue is with the grid view of the blog and with gallery grid element, probably in other places too… Please fix this in any of your future versions, as it’s a shame to be aware of the srcset attribute in img tag and not to use it everywhere where it could be useful!

            Not to be completely negative here – I can see other problems fixed in 4.2, that were annoying in the past, so yeah, theme is definitely getting better 🙂

            Let me know if you need to discuss any of the/other issues through another channel. I’ve said everything I felt like sharing under the post already.

Leave a Reply