I have been using LESS as of late and can't imagine going back. It
is a little difficult at first but a HUGE time saver especially in
creating reusable and/or responsive modules. Live editing is
already supported in Chrome. I would be surprised if css
pre-processors aren't the standard way of doing things in the next few
If some of you folks haven't
looked into it, I would invest some time and check it out
- worth it!
We had some glitches with our support ticket system. We applied the
latest updates and something didn't take. THAT's why we do
We had to do an uninstall and re-install and then sync it up with
the backed up database. It's all working now, and as far as we
know we preserved all the current, and past tickets. That being said,
if you feel that a ticket you posted is not being responded to,
please accept my apologies and please create a new ticket.
This has been such a helpful discussion! The web landscape has
changed so much in the last couple of years and it is vital we make
Cartweaver fit into that landscape, and do it in such a way that is
flexible enough to keep up with it as it continues to move and change.
For quite a while Macromedia and then Adobe tried to make
Dreamweaver the one super-tool that would do everything for everybody
- a lofty goal that they could never pull off... Really how could
they? That's just too many things, moving in too many
directions, to ever be able to handle with one tool. They found that
by trying to do everything Dreamweaver was getting to the point where
it didn't do anything really well. So they refocused and began to
develop more tools that do smaller pieces of the pie very well and
could still work well with tools that do the other parts of the
"pie" - As Edward stated.. this is panning out to be a much
Cartweaver will be making changes to work better in the
"fractured landscape" as well. CW4 made a big move in
this direction by not being dependent on Dreamweaver extension and
being as easy to use for the code developer as it was for the
Dreamweaver user... But there is a lot more we can and will do to make
it much more up-to-date and flexible. Keep the feedback coming.
I have worked on some personal projects involving FB Login. Be prepared
for some frustration, since FB has so many version/docs, that it is easy
to lose track of what is what !
I have used in the past a PHP library , found at http://www.oauthlogin.com/
At the time, it fit my needs of simply getting a user's full name,
email, and birthdate.
The biggest hurdle I would see, is that I doubt you can get all the
actual info you need from a simple FB set of info. For instance,
all the billing info, I doubt it is something you will be able to get
properly. ( how many people do you know that give FB their full address
Perhaps you have just use the FB login, as a way to get a basic set of
user info, and pre-populate the guest checkout form ?
No - straight HTML, jQuery and CSS, with some SSI for consistency in
menus, headers/footer, or wherever I needed to repeat code chunks. I
used Firefox's Web Developer Toolbar, Resize -> View Responsive
Layouts for my guide in media query breakpoints. The site was designed
with an emphasis on tablets, which now constitute over 70% of their
traffic (c. 10,000 visitors daily). I wanted a site which was fast and
reliable, the client asked for a Google page speed of great than 60/100
mobile and 70/100 desktop. Using the above methods I got it to 72/100
mobile and 85/100 desktop without excessive caching/compression. A
framework would have really slowed things down. Interestingly, I have
also managed to replicate these speeds in the Cartweaver shop.
I am familiar with most frameworks, as I freelance for a fair few
digital agencies, who always have specific requirements, but on this
site I was given a free hand, so I just got on with the
Cartweaver support always tries to help out as much as we can. We always help with Cartweaver application issues, and I'm sure many here on this forum will agree that we so often go above and beyond to help with other questions and issues as well... all for free, while other companies have gone to much stricter paid-support models. This has been the way we have handled support from the very beginning, and we take great pride in this.
That being said, as I'm sure most everyone will agree, there is a point at which we have say, this isn't our "ball" and we have to hit it back over the net. There are so many plug-ins, applications, and frameworks out there we can't possibly know them all, let alone offer trouble-shooting or support for them. As you apply these to a web site, the way the code interacts with the existing site, be it our code or yours, can introduce conflicts or unexpected behaviors. Working out the differences and trouble shooting this is obviously up to the one doing the site.
If you bought a new car, then decided to change out or "hot rod" the fuel injection with third party parts, then ran into trouble with the way the car runs, you can't expect the car's manufacture to fix your problems, especially not for free.
We understand, sometimes we can get ourselves in a bind and maybe even be in a deadline situation so we will reach out to whom we can for help. We appreciate this and really try to help as much as we can to, but we would also ask for understanding when we have to lob the ball back into the user's court and say we can't help with this one.
I'll jump in here to clarify as this is a common and valid question, so here goes.
If you hire a developer for tech help with your site they can have access to your site and work with the files as they would any other CF or PHP based web site. Most times since the CW code is so well documented with in-line comments this is plenty sufficient.
What you cannot do is share your Cartweaver download or Cartweaver DW Extension file with them. They can not make a copy of the files to be used on any other sites and they can not receive tech support for any questions they may have, for this they would need to purchase a license themselves.
All pretty straight forward and fair I think you'd agree.