[alibey]

closing this out

[alibey]

$50 to modify a few messages?!!! Thank you for alerting me to the existence of this plugin, but the business of WooCommerce increasingly seems to be to ship something so bare bones as to be of limited use, and nickel and dime the end user to death for the functionality needed for ecommerce. Looking at the various plug ins a retailer would need, I can easily see getting to 300 – 500 dollars, which begs the question why not go to Shopify, and let them worry about the hosting. Do not get me wrong, I think Atelier is great — although I would definitely use the Revolution Slider, were it not for the security issues.

cheers,

Ali

[alibey]

im not wasting any more time on this. there is some mysterious border overlay going on that cannot be identified, which perplexed me as I did not realize there were design elements or effects not available to the end user to change. maybe this is some php thing 😉

anyway i covered up the problem with a cosmetic hack

.post-14915 ins .amount {
…
background-color: black !important;
border-style: solid !important;
border-width: 2px !important;
border-color: #191919 !important;

}

[alibey]

hi Mohammad,

this css does not quite actually solve the problem, but it gave me the idea to attack the problem form the tooltip angle. will work on it and let you know how it goes.

thx

ali

[alibey]

hi Mohammad

My approach in terms of general principles would be always to return the user to where he/she came from.
To go from HP -> cart -> return -> to shop (instead of back to the HP) would be bad UX IMHO
I will see if I cant apply the JS code I sent David Martin last night to fix this. If not, I will have to bite the bullet after launch and muck about with PHP unless I can use that HTML editor window that I think I saw somewhere in Atelier to add an extra button to that page. Just so you know in general I favor the SPA client side JS/HTML5/CSS3 approach to solving all of life’s problems.

cheers

Ali

[alibey]

Thank you Mohammad for your quick response.
A quick look at this plugin revealed the same shortcode / user unfriendly approach that WooCommerce always seems to favor.
I will check it out and report back on any problems.

On a philosophical / design note, it is becoming a bit tiresome to keep discovering that basic, rudimentary functionality (such as the ability to customize messages) becomes in the WooCommerce world Yet Another Plugin or PHP cusotmization (I can probably do most of these with CSS/JS/MySQL, but I am an IT guy: store owners are typically not).

Plugins are annoying to end users, and by constantly using them in lieu of a full featured complete product WooCommerce is shifting the burden of product maintenance complexity to store owners who constantly have to check if, say, updates will destroy their business overnight.

Perhaps Automatic will consider repackaging WooCommerce as a complete solution, with out-of-the-box full featured functionality, and a front end designed to be used by non-programmers, all under 1 fully-tested and approved plug in umbrella, instead of this annoying diversity of plug ins (the more useful of which of course cost money) that some unfortunate end user store owner has to constantly worry about (to wit, the Revolution Slider hack debacle).

I deal with retailers all the time. Retailers dont know plugins from shinola, to use a colloquial Americanism, and simply have no patience for dealing with short code hell. And Woocommerce/Atelier no longer becomes this cheap solution if store owners have to keep running (at who knows what hourly rate) to MN to actually have something that works 80-90 per cent of the way they want it to. My guess is that they would be willing to pay a higher price for WooCommerce — which ideally should include a completely managed hosted solution: try getting the average SMB retailers to deal via chat with bandwidth / performance / spam / SLL issues with, say, those very helpful and nice Bulgarians… not a happening thing in my experience.

I for one dont know why it has taken WooCommerce 5+ years to get to this stage, after forking off the initial work of some English dudes who fell by the wayside due to who knows what reasons. I could probably hire 2 talented developers and design a solution for them to bang out an equivalent product in 3 months — one that is probably not as immature and functionally anemic as the WooCommerce solution, but then again, Woocommerce does have to deal with the PHP back end in which everything is semantically a type of post.

It is time for a product that is actually provides a complete turnkey solution to SMB retailers to hit the market. SMB retailers deal with razor thin margins, and simply do not have have the time available that it takes to use WooCommerce, IMHO, if they expect to be able to run the business AND populate their catalogs etc — WooCommerce needs to be more powerful and much simpler going forward to achieve any success or market penetration beyond wonky verticals.

Maybe WooCommere / Automatic should consider this in the future.

[alibey]

Hi David You can do this without resorting to PHP! Just a few lines of simple JS without mucking about with server files.
Here’s how:

window.onload = function() {
prepEventHandler();
}

function prepEventHandler () {

var myClass = document.getElementsByClassName(‘continue-shopping’);
myClass[0].addEventListener(“click”, function(e) {
e.preventDefault();
window.location.href = document.referrer;
});
}

There is an even faster method of implementing this “customization” (which should have been there from the start, IMHO) that takes fewer lines of code and only 1 func and does not make use of preventDefault.

Cheers,

Ali

[alibey]

Hi Mohammad,

This works perfectly, and completes the UI testing / customization portion of the site. Thank you!

Today we will be testing the STRIPE back end and contacting Woothemes for any Woocommerce-related issues.

I want to say that everyone at Swiftideas has been very helpful, as I struggled last week a bit to learn how to use Atelier and began to customize per my client’s requests.

I appreciate your patience during that process enormously.

Although I do think there is always room for improvement, particularly on the Slider/Shopping Cart integration and presentation side, and also on the Woocommerce category/tag side (per earlier tickets), Atelier performed as advertised — my client will very soon have one of the most sophisticated ecommerce sites in her SMB retail space, without having to spend an arm and a leg.

Barring Hurricane Erika wreaking havoc on Monday in South Florida, we plan to go live this coming week.

cheers,

Ali

[alibey]

This reply has been marked as private.

[alibey]

i have it. just minor styling now. so ignore this. thx!

[alibey]

This reply has been marked as private.

[alibey]

This reply has been marked as private.

[alibey]

solved wrong shortcode this one works but as usual css needed to prettify

[add_to_cart id=”99″] —

[alibey]

all sorted out. i got rid of quickview and make the product descriptions visible via css.

[alibey]

hi ed,

I am closing this topic, and may start a different thread regarding the swift slider. User acceptance testing has started on the site i the US, so that will drive my feedback or any tickets. My client has a bit of a following in the needlepoint world, so the feedback should be very interesting, not just re my client’s site, but how atelier works from a UX perspective with a particular demographic.

Just so you know, needlepoint canvases (which is what my client sells) have a moire problem that is very difficult to solve; it is not a simple matter of taking a standard product pic and gimping it. This is why the pics need to be extremely large (800 by 800 works best, often thumbs from an image that size will look fairly horrible because of the moire issue. so 1200px w is even better, and start to greatly reduce if not eliminate moire, although there are other tricks that can be used), although of course I run them thru tiny png to try to keep them under 300kb.

The main issue I have found regarding pic sizes in the Swift slider so far is that specified the slider image by hand does not produce reliable results, such that if height is custom sized in the add slider panel to say 500px with proportional width, the actual result is an image that is far smaller than 500px h and looks fairly crappy.

will keep at it, and let you know the results later.

cheers,

ali