Loading Profile...
Custom HTML - Where has it gone?
What has happened to the custom HTML facility in Pbwiki 2.0 settings page. My wiki is upgraded to platinum!
I’m frustrated
3 people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company is working on this problem.
-
Inappropriate?WEIRD. Email support@pbwiki, so we can take a look at your wiki. If it's something that is easily remedied, I'll update on it here, but if anyone else has this issue, also email support@pbwiki.
Thanks! -
Inappropriate?Hi Casey,
Can you or someone else please come back to me about this. The matter has not been resolved.
I’m frustrated
-
Inappropriate?Hi Seanmac, are you talking about the Custom Head? -
Inappropriate?Hi,
I just talked to Brian Klug in engineering and Custom Head HTML should be back soon, but they've been working on shoring up some security issues, and that's why it has been disabled in 2.0 for the interim. No ETA, but it's high on engineering's priority list and they've been working hard on it for the past week.
Thanks for your patience,
Vu -
Inappropriate?Hi Vu,
Thanks for letting me know. I wish Pbwiki would give some advance notice of things like this. I have already put something in my Custom Head and now I can't edit or work on it. It just very frustrating. When is it due to come back online?
I’m losing patience!
-
Inappropriate?This is so typical of PBwiki. It's bad enough that they advertise these capabilities, convince people to pay for them, then disable them with no notice. But if they can disable the ability to access the feature, then they could also disable the loading of the HEAD code. I've had a trouble ticket open for DAYS asking them to stop loading the HEAD code that I can no longer access, and they just refuse to respond.
I suspect that if I were a business-class customer, I'd get real support.
I’m angry that they break things with no notice, no response and no recourse
-
Inappropriate?Hey there Guy, I'd just like to point out that I handled your support ticket personally and contacted you about saying that this had been submitted to engineering.
As Vu mentioned above, "I just talked to Brian Klug in engineering and Custom Head HTML should be back soon, but they've been working on shoring up some security issues, and that's why it has been disabled in 2.0 for the interim. No ETA, but it's high on engineering's priority list and they've been working hard on it for the past week."
Please keep in mind that as a beta tester we made it very clear that some features (like the Custom Head) would go away after the beta period.
I appreciate your patience with us. We're working on a large list of task items, and we will get to this. In the meantime, you can always follow up with us through your support ticket if you have questions about the status of a problem.
Thanks! -
Inappropriate?"Please keep in mind that as a beta tester we made it very clear that some features (like the Custom Head) would go away after the beta period."
Yes, but the Custom HEAD did not go away - that's the problem. It's still being loaded. The fact is, the engineering staff could have easily stopped loading Custom HEAD code when they turned off the interface (and when you "made it clear" that it would "go away", that's what I thought would happen - you'd stop loading the HEAD code).
The fact that they are working furiously to fix the 'Settings' link is also irrelevant to my case. I do not have a premium 2.0 wiki, so I will never see that interface when it does get fixed. I'm afraid that my code will still be getting loaded, with no way for me to remove it.
I appreciate the fact that you gave my ticket to Engineering, but that doesn't help me at all. Your response, while personally composed, is no more useful that an automated responder sending "we have submitted your ticket". When I say "no response", I meant a meaningful response regarding the issue at hand. There's no reason to follow up through your support ticket, because there's nothing you can do to fix the problem.
I’m sorry if I seem brusque, but it's not that hard to admit and fix mistakes, especially small ones like this
-
Inappropriate?Guy, I understand your frustration. I've escalated your particular ticket once again, and hopefully the engineering team will get to this soon.
If you have particular concerns about a case, please follow up with it through your ticket. This allows us to escalate it properly in our queue, and to keep track of what's going on. I'd appreciate it!2 Comments
Add a comment
This solves the problem
-
Fine, I'll try that. How do I do that? -
When you open a ticket, you're sent an e-mail back with the case number. Just respond to that e-mail and it will get assigned to your case. You can always e-mail support@pbwiki.com too, and we'll tie it together. Thanks Guy!
-
Inappropriate?There was a very minor bug that was making previously entered Custom HTML in the header load, even though you couldn't edit it, as several of you noticed, but we've fixed that just now, so it will no longer load on your wiki page.
This fix will be deployed later today (I'm thinking in a few hours most likely), and I just wanted to toss a heads up out there.
The HTML you've entered will still be there when we turn it all back on, but it won't be loaded.
Thanks for pointing it out.
1 person says
this solves the problem
1 Comment Add a comment
This solves the problem
-
Bless you, child. :)
-
Inappropriate?I'm still not seeing Custom HTML in my 2.0 settings -- 11am on Saturday, April 12. FYI.
1 Comment Add a comment
This solves the problem
-
Still waiting... 23 April
-
Inappropriate?Have we got an ETA for when the Custom Header HTML editor will be back online
-
Inappropriate?Thanks for the reminder, Seanmac. I've added this feature to the Missing Features Wiki.
I’m missing my missing features
-
Inappropriate?Hi all - just an update to let you know we are still working on this. There are some security-related pre-requisites we need to fix first. We do take security seriously, so please understand this is the reason for the inconvenience of not having the Custom HTML feature.
I’m happy
2 Comments Add a comment
This solves the problem
-
Have we got a vague time-line on when this should be back up. Well not too vague!
-
Come on, Sean, you know better than that. PBwiki doesn't *do* "timelines".
-
Inappropriate?Brian, just out of curiousity: what sort of "security" problems could you be having? Back when you decided to implement this feature, the security implications should have been obvious, and dealt with before you ever announced it's availability (and started charging people for it).
I’m glad you're happy charging money for non-existing features. I think that's called "bait-and-switch".
-
Inappropriate?I've talked with Brian at length about the security issues, and they are indeed legitimate. I don't want to divulge too much here without proper authorization from the folks higher up, but they are working hard to get the custom HTML feature back. After talking with him, I agree that the security measures absolutely have to be taken care of first.
Thanks for understanding,
Vu
