Booc, PageBuilder and the Product Details Component

[lesliekirk]

There's a whole section in the Miva Docs explaining how to add PageBuilder to an existing template, which is fantastic. But what's missing is a "warning" that some features/functionality may not work (this applies to all older ReadyThemes, not just Booc).

In the case of the Booc ReadyTheme and the Product Details Component, the Add to Cart functionality is not working as intended for Booc. There are two functions that are not working with the Add to Cart

1. global-mini-basket-drawer
2. mini-basket__count

The "drawer" doesn't slide down, and the mini basket count doesn't update. I suspect the only "fix" is going to be to create a new component that includes them - please confirm.

And now for my next PageBuilder rant. I still love it, but there needs to be some sort of notice or warning for/to store owners that using PageBuilder with older ReadyThemes (like Booc) may not have all of the functionality of the ReadyTheme.

[PCINET - Andreas]

I had last week a client who had exactly the add to cart issue. Is it your client? Just email me directly :)

[lesliekirk]

I had last week a client who had exactly the add to cart issue. Is it your client? Just email me directly :)

PCINET - Andreas - you've got mail!

[Nick]

I think this is more of an issue with the Booc ReadyTheme being extremely outdated. My suggestion would be to not use that theme or at least make sure that the JavaScript is updated to the standards of today. For example the Booc ReadyTheme does not use the JavaScript resources to serve the JS files (or CSS), it also uses jQuery and does not have other modern ways to implement features that PageBuilder Flex Components use.

[lesliekirk]

I think this is more of an issue with the Booc ReadyTheme being extremely outdated. My suggestion would be to not use that theme or at least make sure that the JavaScript is updated to the standards of today. For example the Booc ReadyTheme does not use the JavaScript resources to serve the JS files (or CSS), it also uses jQuery and does not have other modern ways to implement features that PageBuilder Flex Components use.

Nick I agree 110% that is why I suggest some sort of warning for/to store owners that using PageBuilder with older ReadyThemes (like Booc) may not have all of the functionality of the Components or may not even work at all.

[Nick]

That is the intent with the depreciated message in the app store.

The framework is depreciated and does not work with new features unless manually updated.

This is not limited to just PageBuilder. Any new features since the framework was depreciated can be consider unavailable.

[lesliekirk]

That is the intent with the depreciated message in the app store.

The framework is depreciated and does not work with new features unless manually updated.

This is not limited to just PageBuilder. Any new features since the framework was depreciated can be consider unavailable.

It hasn't seemed to stop people from using these depreciated ReadyThemes. Maybe a few more warnings, maybe one when it's being downloaded, maybe a checkbox "I understand this ReadyTheme isn't going to be able to do all the new neat things that Miva can do and might even break if I try to". Maybe a warning when it's being applied: "Hey, I see you didn't heed the warning, proceed at your own risk."

Then maybe a warning at the Upgrading to Page Builder docs: "You really shouldn't try to add PageBuilder to these ReadyThemes unless you want to hire a developer to spend lots of hours making it work for you"

Hopefully, you get my point. The initial warning is being ignored. Use some humor to catch the attention, or just remove them from reach. This is the second depreciated, out-of-date ReadyTheme that I've been asked to peek at, only to find it was some sort of PageBuilder conflict.

[PCINET - Andreas]

It's a real pity that none of them got updated. Assume because of marketing they are still listed but can't be downloaded anymore. I think all of them could be updated using latest shadows as base but who will do it. I agree with Leslie to emphasize that new features will not work or will require custom coding. Store owners are not developers and don't get always the meaning ;)

[Rick Wilson]

We'd certainly support any of the dev community taking those legacy ones and rebuilding them on Shadows/Page Builder and offer them for Sale.

Otherwise our resources are still 100% focused on making sure all of Shadows is modern and Page Builder based. The idea is to eventually have a B2B theme and possibly a couple other D2C ones that are Page Builder Shadows Derivatives, but we're far off from touching those and would hold off if the Dev community took hold around it.

[PCINET - Andreas]

Rick, I don't think the market is big enough to have a ROI for such a task. Are you planning to come out with your own (shadows based) RT again? The RT page promotes colossus which is depreciated.

[Rick Wilson]

No, the concept of Ready Themes is also deprecated. Shadows and Page Builder replaced the idea behind it, I'm not sure what you'd do in a Ready Theme of Shadows that you wouldn't do with Page Builder?

There are still some controls labeled Ready Theme but we're slowly moving all of those controls into Page Builder.

[PCINET - Andreas]

gotcha! Just thought that shopify has over 500 theme templates and having this for Miva could help future customers to pick Miva and not shopify :) PB just makes it easier but RT were pretty neat so why not have templates too. Just asking and we can discuss at camp miva!

[Rick Wilson]

You can still have Templates, they've always just been Frameworks. We're not going to work on a #2, Shadows is #1 until everything is in PageBuilder. At that point depending on where we are we might add a #2. Unless some Devs start building some.

As for Shopify's 500 themes, yes it's something they have that would be hard for us to match, but from where I sit, I don't think it we magically had that, we'd increase signups much if at all. It's hand to hand combat for new logos these days (just follow Big Commerce's results). I suspect those themes are largely for the cheap plans at Shopify which have an average lifespan of 6 months as a client. We simply don't sell to those types of clients anymore.

We're essentially selling against Shopify Plus.

[PCINET - Andreas]

makes sense if competing with shopify plus. Yonka is on it and they pay the same amount as on Miva. Made no sense to switch but France made them switch.

[Rick Wilson]

How can we bring them back?