Oh I tried. Prior to this problem I had a problem with commentsStack. Rather than use the FA icons I’d made a site specific icon font that used part of the logo for the ratings “star” display and it mostly worked until one clicked on the rating.
So I sent an email with the font, the changes to his example code and several screen shots showing how the problem manifested itself, and it could have been utterly replicated with what I’d sent.
I got a reply of:
Unfortunately screenshots on their own are not really sufficient. Yes they certainly can be useful to illustrate issues, but ideally I need code to run diagnostics on and use tools like the web inspector. That’s about the only way I can troubleshoot CSS, within my abilities.
I know a lot of RW developers who will flat-out refuse to offer any help whatsoever with custom modifications, even if you tried to bribe them! Some probably will not even reply to your emails! Thankfully I’m different.
But to help you, you really do need to put together a more complete support case for me to review. Please take another look at my knowledge base article on requesting support or ask on the community forums if you don’t know what to send me.
The bottom line is that I don’t have the time (or eagerness) to spend a lot of money on addons (like Foundry) from other companies, then several hours to learn how they work, and even more time to piece-together your entire page setup again. It’s not really fair on me, considering you may have only paid $30 for the stack. Regretfully it’s just not sustainable for me to operate like that and dedicate that much time to one person. You’ll need to provide everything to save me some time and money, if you are wanting help with this.
I then spent a couple days chasing why it didn’t work stepping through the code in a browser debugger, making one change at a time inside RW and then running diff’s on the output code, and read through YourHead’s docs on the Stacks API and finally found that the problem was that no user could have made it work because he had template code that was in the the pList of the stack that would get bolted in effectively overwriting anything an end user might have included in the user editable CSS field.
So I cloned the stack, made changes to the pList so it’d work with another font and sent a project file that had one page with his stack and page with the changes in my cloned stack, and he apparently got bent out of shape that I had the audacity to suggest that he may have an actual bug.
Reply was essentially that no one had problems with it, he didn’t have problems with it, and that he didnt’ have the time to deal with other stacks (foundry or foundation).
The reality was there was no issue with foundry, or any other non Will supplied stack, it really was an implementation issue on his side, and I’d even shown him exactly where in the pList file the bolted in code showed up.
Meanwhile, I was running into this problem here, and it would even show up in his example stack with absolutely no changes whatsoever by the end user.
So I sent this over:
I wish to demonstrate something that you may not be aware of, and will provide the simplest step by step instructions to replicate a possible issue:
1 Open your MiniCookie example project.
2 Enter preview mode.
3 Hit Delete all cookies to make the pop up appear.
4 Set any combination of cookies you wish, but turn at least one of them on.
5 Hit save settings. You should see “dismissed_popup” and whatever cookies you had chosen as both present, and true.
6 Delete the “dismissed_popup” cookie to make the pop up appear again.
7 Notice that whatever cookie you HAD set previously is NOT checked, even though it is actually set (which you can see at the upper part of your page).
8 Click Save Settings. The pop up goes away, and even though the checkboxes showed that nothing was set, whatever you previously had set still is.
Apparently the step by step stuff was not sufficient, and he had took some offense to my altering the commentsStack to demonstrate where the issue in that stack occurred, and the next reply aside from “No body else has had this problem and it’s working fine for me”.
I went to https://bottletreeworx.com/ but the website is broken or offline. Nothing for me to view, in regards to CommentsStack or MiniCookie. So at this point in time, you’ve essentially exhausted me and I can provide no further assistance to you.
(Well of course not, the site hasn’t been published yet and was only running on a sandbox server in house, and I’d explained that). He then ended with:
I suggest going forwards, that you use the RapidWeaver forums from now on. It appears I am unable to satisfy all your requirements. For 16 years I’ve provided free trial versions of everything I sell (and offer more free addons than any other developer does), so in future I suggest you try these addons before committing to a purchase, or just exclude me from your list of preferred developers and buy from someone else. I’m unable to dedicate any further time or replies to you.
When I sent over the project file I linked above it bounced back saying he’s blocked any incoming emails from me…
So that’s why I’m posting here. I’ve never had a developer block emails simply because they were tired of hearing about a problem a user had with their product. It’d be one thing if i was really stepping outside the bounds of the stack’s intent, but the customization of the display of the ratings in CommentsStack was an advertised feature that he marketed, and the multi-select aspect of MiniCookie was also touted as a key feature, and because I actually tried to use those features and they didn’t work because maybe no one else had actually tried to use them is sufficient reason to block me? Wow.
I used RW 10 years ago to build a site that was getting a couple hundred thousand hits a day in it’s heyday but hadn’t done anything web wise since until this project. The responsive stuff, cookies, stacks, that’s all new but I’ve noodled out most of it outside of these issues.
But I’ve looked at the stack you linked above, and it appears to do exactly what Will’s stack does (looks a little different, but that’s ok, I can deal with that), and has the bonus of having been tested with framework stacks like Foundry and Foundation. I’ll give that a go. Thanks.