Digital experiences for all disciplines
New Landing › How can we help? › Atelier › Stroke to fill buttons missing css
New Landing › How can we help? › Atelier › Stroke to fill buttons missing css
- This topic has 16 replies, 4 voices, and was last updated 9 years by Mohammad – SUPPORT.
-
Posted in: Atelier
-
October 20, 2015 at 1:16 pm #221901
This probably is within the Swift Framework, but anyways…
Using the “Add button” gives us some options to insert a button without entering the shortcode by hand. But looking at “Button type” we have two options, Standard and Stroke to fill. But there seems to be missing some css for the stroke-to-fill:
a.sf-button.stroke-to-fill {
background: 0;
}We could however change the type manually to “bordered” which is previewed on the slider at the demo page:
But not all users understands this, so you should probably update the css. I’m guessing you changed the name from “bordered” to “stroke-to-fill” but forgot to update the css ๐
Cheers!
October 21, 2015 at 11:19 am #222142Hi,
Do you mean the button on the Shortcode generator or the button asset in the Swift Page builder?
-Rui
October 21, 2015 at 11:39 am #222152Oh sorry, this is through the Swift Slider “Edit slide” page. Don’t know if it appears anywhere else.
But I can see that the Swift Page Builder also uses stroke-to-fill class on buttons.
Attachments:
You must be logged in to view attached files.October 21, 2015 at 12:35 pm #222175Thanks for the clarification.
Will forward to the development team.
-Rui
October 21, 2015 at 3:43 pm #222263What version of the swift framework plugin are you using? We already have this css:
a.sf-button.stroke-to-fill { background: transparent; }
– Ed
October 22, 2015 at 12:20 am #222376I’m using Swift Framework 1.63, which is the latest version available at the moment. Though it is mentioned in the Atelier 1.74 Changelog “Share buttons now open popup rather than new tab (needs Swift Framework v1.64+)”.
That would be my next question, my dashboard keeps telling me that there’s an available update for Swift Framework. However the update available is 1.63, the same version installed…
Could you give me a direct link to a later version of Swift Framework if available please.
October 22, 2015 at 9:47 am #222426This reply has been marked as private.October 22, 2015 at 10:16 am #222439Swift Ideas โ Ed:
Yeah, but right after you have:a.sf-button.black {
background-color: #222;
}So black buttons with stroke to fill does not work.
Rui Guerreiro:
It is still version 1.63October 22, 2015 at 10:27 am #222443Yes, 1.63 is our last version but something could have be wrong after your update, that’s why I ask to upload this files I sent.
Did the notice go away?
Will leave the other question for Ed.
-Rui
October 22, 2015 at 11:44 am #222494Nope the problem is still there, it tells me there’s an update available. Deleting site_transient_update_plugins from tables does not help either.
I do remember I got a debug error from wp-updates-plugin.php line 79 if that helps:
'version' => (isset($plugin_info->checked)) ? $plugin_info->checked[$this->plugin_path] : 0 // Current version
October 22, 2015 at 1:32 pm #222530v1.64 will be released today – not sure why you are receiving the update notice, checked here and don’t get it on any of our sites.
Have tested the stroke to fill button locally, and can’t replicate any issue – can you provide a link where we can see the issue?
– Ed
October 22, 2015 at 2:20 pm #222544I’m afraid our test site where I’m using Atelier is hidden by IP. But look at swiftideas.com
Right click the “Learn More” button in the slider and inspect.
Change
<a class="sf-button large black bordered
to
<a class="sf-button large black stroke-to-fill
And it will replicate the issue.
October 22, 2015 at 2:54 pm #222564Thanks – able to replicate now, will get that sorted.
– Ed
October 22, 2015 at 10:22 pm #222666Well, you probably just have to move the
a.sf-button.stroke-to-fill { background: transparent; }
further down in the css, hence Cascading Style Sheet ๐
You can mark this thread as resolved now.
Cheers!
October 22, 2015 at 11:07 pm #222667I am aware of that! Already done.
The issue must have arisen with the consolidation of the css to the plugin from each theme.
– Ed
-
Posted in: Atelier
You must be logged in and have valid license to reply to this topic.