I just upgraded my site to v2, where there previously was raw HTML code, there are now objects (question mark images). I also can not choose to Edit Raw HTML from the Edit menu. I can select Insert->Raw HTML.
Similar experience here. I upgraded and get little red "invalid html" badges everywhere I had custom html - I can't bring up an html editor window either.
Same problem here. I'm new to sandvox and was excited about it but it looks like I'll have to try 1.6.8 instead
I've just updated from v1 with PRO features fully working, and installed the _Sandvox-23315.dmg file downloaded from the official website.
The app asked me (some little remider in green on the upper right corner I think) to update registration, and I clicked on it. Then a full dialog window appeared with my new registration code already inserted and saying that "Sandvox is already registered. Thank you", and offering bellow the options for a full purchase...
After closing and exploring the new interface, I tryed to edit raw HTML but the corresponding menu item is always faded and unselectable. I get no little red warnings on places where my custom HTML should be, and the site looks apparently the same. But no HMTL editing feature...
Some other hints to the lack of HTML editing feature after installing v2:
For renewal I started using the link on the e-mail I received from Karelia announcing v2 release.
After the payment process I received a new single user license (v2) starting by a different name of my former single user pro license (v1). I should have change when I used a slightly different payment method, but I always intended to upgrade, as I finally think I did... But no HTML editing any more.
More details I think may be relevant:
When I try to recover mi user license code using the "Retrieve Lost Code..." function on the Sandvox registration screen I only get by e-mail the former code (for v1 pro), though the new one (for v2 after upgrade) works fine (except HTML editing).
The HTML edit of v.1 is gone. Now there are raw HTML objects. Anywhere in your old site that you edited the HTML will need to be recreated using the raw HTML object. Put your cursor where you want the raw HTML to be inserted. Select raw HTML from the object menu. I have gone to my old site , view source, copy and past the code into the HTML window in Sandvox. I had to do this for various parts of my site. HTH
This is unacceptable. I need to insert the special code for Amazon Associates links IN THE TEXT, as linked words IN THE TEXT, not as some separate object. I could do that easily with Edit HTML. Right now, I don't see with Sandvox 2 how I can do this. Unless someone tells me how I can do this, I am going to demand my money back.
Today it seems as if many people is suffering from the same problem, and it has probably nothing to do with registration issues. It may be a bug.
I would ask everyone to update to 2.0.2 and re-import your .svxSite documents again. If you're still having problems, please contact Karelia Support. Also, check out the sticky post on Raw HTML.
I'm afraid updating does not help at all. Judging from another post on Raw HTML, Karelia just decided to eliminate much of the ability to edit raw HTML. That is unfortunately the ability I need. So I will try to contact Karelia Support, but I imagine that there will be no option and I will have to demand my money back. Since the old version of Sandvox is now gone, my site is dead and I will have to search for another software.
We'd certainly like to hear your feedback at Karelia Support (link at top). We are making some adjustments to raw editing based on feedback, though the overall direction is to keep a bit more separation in version 2.
Just for clarification, the older version of Sandvox hasn't gone anywhere. There is a link to download it (under the big green button) right on the sandvox.com page.
I just got the response from Karelia Support. As I feared, Karelia has changed raw HTML editing so much that I cannot even do the very simple things I used to do. This is not a bug: it is a conscious decision by Karelia. I can only say that Karelia has made a big mistake doing this. I will try to go back to version 1, but I am asking for my money back and also will search for a software company that actually allows me to do what I want to do.
I hate this.
I was perfectly happy with the old system - I could type in my text and toss in a couple of html tags here and there as needed. Now, if I want to make one tiny change to my text I have to hand code the whole frakking object. Argh. Yes, I know that with the old system I got lots of extraneous code stuck in there from god knows where, but I always cleaned it out. It was so easy to get what I wanted.
The 05/13/2011, that is, a few days AFTER I bought Sandvox v.2, you can still read on Karelia.com:
"...Edit Raw HTML: Click your mouse, choose any text element on a page or in a pagelet, and you can edit it as Raw HTML..."
I saw it BEFORE buying, decided it suited me as a previous user of v1.6.8, and payed the price of v.2. Now I'm sure I've been deceived, because the web page where I read that has significantly changed: no more HMTL editing as before. So this is bad publicity, I'll ask my money back.
Futhermore, I will stop using the application, and it's a pity because I really enjoyed Sandvox very much.
Wrong Karelia decission, Terrence, which could be somehow alleviated if some "transitioning" plug-in would be offered to convert selected page parts into custom HTML blocks...
Raw HTML objects are not an acceptable substitute for the ability to edit the body HTML directly. For example, resizing the HTML object is pointless if the object takes up the entire width of the page regardless; there is no ability to wrap text around an HTML object, or position an HTML object next to a photo object. Using a rich text editor to create and paste a list into the body borders on ludicrous, since it will paste in much more formatting (font face, size, etc) than just the <li> tag.
I write recipes; unordered lists (ingredients), ordered lists (procedures) and tables (nutritional values) are not optional for me. I have spent several frustrating days trying unsuccessfully to develop some sort of work-around that makes sense and does not waste enormous quantities of my time. Apparently, Karelia, you are shrugging and suggesting that I return to 1.6.8 as my best solution.
Thanks for everyone's feedback. We are discussing it.
jnaustin, I feel your pain. I don't like having to make an html object every time I wish to employ the simple formatting outlined in the main CSS.
Here's what I've had to do to use CSS for what it was invented for:
Make html object to house page title (size h1)
Follow it up with a text box for what I want to say.
Hey, it's time for a subhead! Add another html object.
And I would like to throw in a sentence real quick to present...
This bulleted list.
And back and forth and so on. It's ludicrous.
I can't imagine that this, or using the font editor, makes for clean code on the back end.
Last edited by MmeMagpie (May 17, 2011 4:53 pm)
"...Edit Raw HTML: Click your mouse, choose any text element on a page or in a pagelet, and you can edit it as Raw HTML..."
I have the same problems with this new version, while there are major good Improvement in S 2, there are some "stuff" that are not working for the majority of us.
Please put back the "Edit Raw HTML" the way it was before the update.
Wow, I am happy that I didn't upgrade yet. I've been busy and haven't had time to sit down and do the process, I'm thinking waiting is the best idea at this point. I played with the demo a bit but didn't like how my site's collections transitioned over. This might be a result of a 3rd party theme.
I ASKED YESTERDAY FOR A REFUND.
Saddly, I'm getting back to v.1.6.8.
Y me voy sin saber por qué Karelia se ha visto obligada a eliminar la enorme potencia de diseño que proporciona la función de editar libremente HTML. Intrigante.
With respect to post #12 wherein Terrence suggests we make our concerns known to Karelia Support: I did just that yesterday afternoon. I got this reply:
"Thank you for writing to us. We're sorry to learn you are unhappy with your purchase of Sandvox.
Please let me know your transaction information (confirmation number from us, or transaction ID from PayPal or FastSpring) so we can verify that you are eligible for a refund, and I will get that processed."
I have been using Sandvox since 2006, and I am a loyal customer. I never had a problem paying for the Pro license, because it let me do (and get done very easily) precisely those things which I can no longer accomplish with 2.0.2. I suspect that Karelia made the decision to go with a single-tier license structure for simplicity, and chose to require everyone to license at the novice level (while assuring us in the ad copy that we were all pros now).
Unfortunately, it seems clear from the reply I received that Karelia has done the cost-benefit analysis and decided that losing loyal longtime customers is an acceptable tradeoff for the new customers they must anticipate this release will draw. I have not yet asked for my refund because I am holding on to the tiniest sliver of hope that 2.0.3 will restore the full HTML editing functionality of 1.6.8. (Or that I will get an anonymous e-mail from Karelia with a super-secret patch that will fix the problem--I swear I won't tell anybody else. Well, except Norber. I would tell him. But nobody else, I swear. Oh, and MmeMagpie. It would only be fair to tell her, too. Or, Karelia, you could just revert to the 2-tier licensing and let us all get back to work.)
It's not a matter of what license you buy. The fundamental fact is that in order to really move Sandvox forward and do the things we've been planning for years to do with it, we needed to rewrite its internal engine for stability. A big part of the instability in 1.x was to let everything on the page be an HTML free-for-all. This created a lot of support headaches for us, not in answering to bugs in Sandvox which we're happy to do, but in straightening out other people's HTML. We made a very conscious decision to scale this back so that we would have a more stable platform going forward. We really think that will be to the benefit of everyone.
That said, I ask you to contact Karelia Support with your concerns because it does help to let us know how this change is affecting you. Just in the last week, after looking at how many of you were using Sandvox and what was being treated as "raw HTML" during document migration we realized we could relax some of the rules and clean up some of the HTML during migration so that this change wouldn't be as big of an issue for some customers. (The case that comes to mind is the pasting in of junk HTML formatting commands from Microsoft Word.)
As we go forward, we are continuing to discuss what we can do to bring back even more flexibility. The fundamental goals outlined above won't change: where Sandvox 2 draws that line, may.
If you're willing to work with us and hang on and give us feedback, we'd love to work with you. If this change just doesn't work for you and you're not willing to come with us through this transition, 1.6.8 is still available for download.
I received yesterday my refund.
When I considered the v.2 offer upon launching (cheep upgrade for old customers) I was glad to see everyone would be treated as PRO customer. 'That's the way!' I thought. Imagine my deception when I had to ask my money back because we actually where less than PRO... Well, I'm not quite sure yet of the rationale of the decision taken by Karelia, 'a very conscious decision' as Terence says... I think it is not. As he declares, their support resources at Karelia where mostly devoted to straighten out other people's HTML, and that is why 'Sandvox 2 draws that line'. Ok then: we bloggers in this post are paying for other's mistakes. I can't see it differently. And it is not fair.
Dear Karelia team: here you had a devoted customer. Now only a friend.
I'm throwing in the towel. I haven't heard back from Karelia since Tuesday. And I did use the (link above).
Sorry Karelia. You really screwed up a beautiful thing and made me a liar, to boot. I told a bunch of folk about this release and how awesome I was sure it would be. I even shared the coupon code because I wanted people to try it. I'm not sure if I have managed to track them all down to apologize for my grave error in judgment.