• Artan

    (@artankrasniqi1988)


    Well,

    what can I say, I use this theme now for my second project but I′m not sure if I will use it again. First the pros:

    + highly customizable
    + additional addons
    + nice layouts
    + good documentation for developers
    + compatible with lots of plugins as it′s famous

    cons:

    – i ran in so many bugs like weird breakpoints layouts
    – even if you give deep insights as an developer of easy to reproduce bugs, nothing will be updated or repaired. Perhaps someone elses bugs but not the ones I found
    – Support says they will fix things but In my case 0 tickets have been fixed. Better say you don′t do it then trying to be nice. Because people then better can save time and search for other solutions or themes
    – u pretty much have to write tons of CSS to get the rid of inconsistencies at smaller screen sizes or other ugly breakpoints, layouts.
    – grid and flex layouts should be more common in use of layouts. These css layouts are out there now since years and are a better way for responsible layouts then block elments.

    Overall, I think the theme is nice, but the worst thing is that even when addressing obvious bugs, nothing seems to happen to fix them. And if even when giving deep insides how to reproduce them and still in moths nothing happens, I think the theme is perhaps doomed to get overbugged at some point…

    Just my oppinion. I worked hundreds of hours with this theme and can surely say I have a deep look inside it.

    Thx and regards.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hello @artankrasniqi1988,

    Thanks for taking the time to share your experience. However, there are a few things you should know.

    First of all, WordPress org is not one of those places where you can buy themes that have been abandoned for years, not to give them free advertisement so no names for such places. Unless it’s something that requires fixing a critical issue, we will not push changes / updates. Frequent updates are also forbidden by the rules and let’s be fair here, they need to be meaningful.

    I will get to the part “nothing is done” below.

    1. Weird breaking points are not bugs. We also don’t have any weird breaking points by the way. However, a lot of it depends on how you customized the site. Since I haven’t seen your website I can’t comment on that. But if you customize a website heavily then yes, you need to write CSS that will handle your own changes. That’s something all web designers need to be prepared for.
    2. You gave user insights on how to reproduce something. That’s actually how it should be done and we thank you for that. But your reports alone do not dictate OceanWP updates. OceanWP revolves around all its users.
    3. Support techs are not developers. And while they can reproduce something or not, unless they’ve actually talked to a developer and clarified things out, they are not there to fix bugs.

    However, let’s address the part “nothing is done” or “nothing seems to happen to fix them”. On September 13th you received a dev version of OceanWP addressing one of the issues you reported. You didn’t want to test it, which is completely your choice. But the statement “nothing is done” here is false, I believe we can agree?

    I respect your opinion as a user. Obviously, we do take feedback seriously. OceanWP is made for its users, so naturally all enhancement is aimed towards better user experience, improvements, and modernization.

    Since I have spent just a few hours longer than you with this theme and majority of its users, I can tell you that the reason OceanWP is compatible with WooCommerce, Elementor, other plugins and most importantly WordPress – it’s because updates need to be meaningful, but also tested properly with everything. I can also say that 99% of things users report as a bug, are not bugs, and don’t even relate to OceanWP at all or fall under personal requests and due to being stuck with personal customization.

    That being said, the 3.5.1 version has been delayed on my personal request and put towards compatibility with the upcoming WordPress 6.4 release primarily.

    Hope this clarifies things out. And if you want to discuss feature requests or other enhancements, you can seek me out.

    Thank you for building with OceanWP

    Thread Starter Artan

    (@artankrasniqi1988)

    Hi Marko,

    thanks for you honest opinion. Yes, I can confirm that I got a file for a specific problem I had. As it seems, this issue could be reproduced (not aligned megamenu in box layout), and a file got sent to me. I said I will wait until it′s pushed live to get sure it will be in live update and not overwrite the fix when new update comes.

    I also agree to your opinion, that a lot of times users with less experience or knowledge of programming can fast accuse developers of bugs or problems not regarding their products.

    I just have problems with answers like: “Premium Addons for OceanWP have to be seen separated from the FREE Theme, etc.” Yes, you kind of have to distinguish between your products and who is responsible for what. But which customer or user can really distinguish who is responsible for what in that jungle. I think that′s why some are disappointed as they think, if something needs to be fixed, why is perhaps no one feeling responsible for it.

    Support is not dev team, so true. That′s why I said: “It feels like people get back to you but it feels like nothing is happening”. It seems perhaps something gets answered but not passed through.

    I can understand, that updates absolutely need to be meaningful and developers have to see lot of things through. At the end, obvious problems that not only I could ran into, will stay for too long. I just think simply lot of people just don′t report them. I′m to perfectionist sometimes and want things to run smoothly.

    “You gave user insights on how to reproduce something. That’s actually how it should be done and we thank you for that. But your reports alone do not dictate OceanWP updates. OceanWP revolves around all its users.”

    Thanks that′s exactly what I wanted to hear. Obvious reproducible problems that multiple people could run into, even if only reported from one user isn′t “dictating” the developers what to to. It helps the greater good for all users who could run into the same problem.

    Perhaps we both just have different views on how to manage those things as developers. But that′s ok. As I said, at a certain point I just needed to know which “corporate” values you and your developers present and if asking support is consuming my time more then developing around certain problems myself is faster and more economic for me.

    Still thanks for sharing your point of view!

    I will write functions and CSS for the problems I found myself as I can′t wait for months until fixes get pushed live.

    Regards

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Highly customizable but lot of bugs’ is closed to new replies.