Hi Reg:
So let me get this straight…you are saying that a reinstall of Blocs 6, and not renaming the app, fixed your preview issue AND got TAP working properly again?
Rich the Weather Guy
Yes, for me it did. I uninstalled/ reinstalled 6, but did not rename it (I renamed my old Blocs to Blocs 5 to avoid conflict). I then imported a site made with 5 into 6 and TAP works in preview mode. I should edit my previous post, though, because I realise that I can’t preview the site in Blocs 5 because I renamed it and preview no longer works. Also, I haven’t tried to create a new site or add TAB to the imported site in 6 yet, so don’t know if the issue reappears.
I think this is when you will find TAP doesn’t work in B6.
I’m trying it now.
Great…awaiting your results!
Once again, I found that transitions did not work, and the display was not right in Safari, it was displaying ALL panes, until you click on a ink.
Right, this is what I found. When I create a new site in 6 and add TAP, the initial preview shows all the tabs, but clicking on a link returns it to functioning normally. This is the problem you mentioned above. However, for me this is not the case with a site imported from version 5 to 6; preview shows only the first tab and all links/ tabs work.
I only made a quick test and haven’t had to add TAB to a site for quite a while, so there may be something that I’m doing wrong (box not ticking, etc)
You will probably find, as I did, that you will be unable to edit the old TAP you created in B5 in B6.
All sorts of things went bad when I tried. The menu disappeared…strange behaviors, etc…
For anyone wondering, this why renaming the app has potential to break it.
Why Renaming Affects Code Signing
macOS app bundles have a specific structure, and their code signature includes various elements like the app’s executable and the bundle’s Info.plist. The app’s name, as part of the bundle identifier (CFBundleIdentifier in the Info.plist), is embedded in the code signature. When the user renames the app, the bundle identifier and possibly paths referenced internally may no longer match the signature, causing macOS’s Gatekeeper to consider the app invalid.
Blocs gets signed a few times, but I think it may be the DMG installer which is handled by a third party development tool that may be making the app more sensitive to the renaming.
I’ll investigate it further and see if I can source the cause.
But keeping the app name as Blocs will likely fix many of your issues as its no longer being limited by Gatekeeper.
3 Likes
I won’t touch it then! 
Thanks for the heads up.
I’m afraid it is not so easy. I never renamed the app and still have problems with TAP.
I even completely deleted it, re-install but have the same (almost) issues.
My answer is also for @Bootsie.
The issues are:
- the index of TAP shows (number 1 only) in front-end.
- Using TAP with links on images don’t work, also they do work with the TAP bar.
Note that the reason I want to use links is that using images (and not Text) with TAP only allow for fixed sizes from S to XXL but the latest still is small. - The mobile option does not work unfortunately.
Please note that I usually publish the site on a DEV server and not use Blocs preview. And I check with Safari and Firefox usually.
For the time being, I deleted TAP so I can’t show you. But maybe I’ll add it again on a test site and will publish here the URL.
1 Like
And for those who can’t make work TAP in Blocs 5, I suggest checking if jQuery is included correctly in the page source.
I mention this because I had long time problem with this “export jQuery” in project settings. @Norm fixed that, I guess, but as far as I remember, it was not an easy bug tracking.
Here is the Blocs 5 website I did using TAP for main menus (left column).
As described in TAP manual, we have links with interaction Toggle Visibility and Custom Attributes tab-group=x and tab-index=z.
That is the site which rely heavily on TAP (@WeatherguyNH) and I’m scared to edit and publish it in Blocs 6 
.
That is my issued. I relied and used TAP extensively…so I continue to update my site in B5. I will NOT move it to B6.
This looks very close to what I have done with the new BlocsLibrary.com website. Although, I actually used Accordion and Carousel.
2 Likes
For the record I don’t own Tab Anything Pro or any of Whittfield’s Brics. But at one shining moment they were the cream of the crop regarding ability, documentation, everything. The whole downward trajectory since is just so odd how it all ended up.
Whittfield has long been absent but to me it would be his sole responsibility to ensure his offerings continue to work within the product he is using to generate revenue along with supporting his customers. On the flip side to me Norm’s responsibility is to ensure the Blocs Developer API offers this opportunity accurately and effectively for those wanting to do so. Where these two facets all fell apart and why is anyones guess.
In essence officially removing Whittfield’s paid products from the Blocs store was a good indication that maybe users should be cautious or that things were in decline concerning his brics and support within Blocs.
I understand that for those who have Tab Anything Pro or anything else that you rely upon – it sucks.
I know and honestly that itself seems counter to the level of professionalism and integrity he seems to possess if he’s not wanting to fully support what he offered, rather odd in the grand scheme of things.
It’s probably best to move forward with other options as @Eldar has shown. Also once Norm releases further into on the “Interactions Manager” (you’ve already begun testing) that should offer further opportunities for users. It’s also a good opportunity for users to re-think if there are better ways and opportunities to deliver content when reworking their sites.
4 Likes
Nicely done Eldar.
Very smooth flowing…
2 Likes
I recently said the following in an email to one of Blocs users. This has been my public stance for years, hence probably why I’m hated by some of the developers.
«… my golden rule is: if a third-party bric doesn’t bring anything new to the table (it doesn’t expand the functionality of Blocs), it’s always better to stick to Blocs’ built-in features.»
Of course, unless a user wants to save some time, which is totally ok.
3 Likes
Who hates you? No one I know and the dev list is a short list.
The “golden rule” applies to templates and blocs also. All time savers. Most if not all the brics add or expand functions to Blocs that is not there that I can see 
All my brics use pure Javascript, Bootstrap CSS, standard HTML and I follow best practices around accessibility (although always way more to learn there). It’s highly unlikely, unless there was a change in Blocs or something deprecated in Bootstrap, all my brics will continue to work fine in 6 and I provide support to my customers. The best that I can anyway. I wasn’t invited to the beta, so was unable to test my brics earlier on.
5 Likes
The primary reason behind my golden rule is my reluctance to rely on someone else (except the developer of the Blocs app) to guarantee that my Brics work seamlessly with new versions. This is based solely on my personal experience over the past decade talking to users (about issues with Whittfields Brics, Pulse CMS, Blocs Bakery’s Brics, Blocs Guy’s Brics, and others). Blocs and templates utilize the features of the Blocs app and do not necessitate the developer’s input to remain functional.
I am happy to hear that.
P.S. I can expand on what I believe brics should be about (functionality over time saving features), but you probably know that better than me. Ex) I can’t make CMS without code, but I can design cards, so I will always need Volt CMS, but Card Designer is optional (even though it is a great bric I recommended for years).
1 Like
Always look both ways @Norm , twice at least 
.
Has your son started his apprenticeship for macOS, iOS, iPadOS, VisionOS, Swift, etc., etc., etc., to one day take the reins? 
4 Likes
There is always some risk. I recall YummyFTP was all the go, an excellent app, I loved it. Then the dev, a solo indie, suddenly, sadly passed away all too young. And it was left to the sands of time.
In this case, our files were not locked into a propriety system, and adjusting to alternatives wasn’t so bad.
Of course YummyFTP didn’t stop working that day, but eventually it became a problem without updates.
There are some great products made by Indie Devs. I use a number of them, but I don’t put all my eggs in the same basket as they say.
1 Like