snowdogapps / magento2-alpaca-theme Goto Github PK
View Code? Open in Web Editor NEWMagento 2 theme built on top of Alpaca design system crafted for ecommerce
Home Page: magento2-alpaca-theme-git-master-snowdog1.vercel.app
License: MIT License
Magento 2 theme built on top of Alpaca design system crafted for ecommerce
Home Page: magento2-alpaca-theme-git-master-snowdog1.vercel.app
License: MIT License
The current composer.json
file accepts only magento/framework
version 100.1.*
(Magento 2.1.x)
Please add compatibility with magento/framework
version 101.0.*
(Magento 2.2.x)
Will be nice to follow same rules as in the header, so remove as many containers as it's possible and create the layout in phtml file.
There is a lack of css for emails - is it correct?
If I set locales to pl_PL then email templates expect i.e. email.css to be accessible from https:// ... /frontend/Snowdog/alpaca/en_US/css/email.css (Yes en_US)
If I copy email.css (where it exists) file from disk location: pub/static/frontend/Magento/luma/en_US/css/email.css to pub/static/frontend/Snowdog/alpaca/en_US/css/email.css it seems to work. But still urls in mail source code point to the en_US instead of pl_PL.
If I am wrong, could you please tell me how should I manage css styles for email templates?
Missing Page builder styles form Magento 2.3 EE
Refactor whole header related code, the same way as in the Janus-et-cie project, with having in mind that is easier to add and customize template file, than fighting with tens of nested layout containers.
Step to reproduce:
This error occur because Varnish keep invalid old form key inside action attribute. We should update solr and alpaca methods to keep it in 'magento-way'.
To do:
solr-add-to-cart.js
with extended magento catalog-add-to-cart.js
widget and add customerData with invalidate()
method (to keep minicart updated).form_key
from solr, and add dynamic block with no-cached form_key.This theme looks great, but I've been struggling to try and get it to run. I successfully followed the installation steps and ran all the commands, and went in and changed the theme to Alpaca. Unfortunately, when you visit the home page, it's missing all the CSS . When I check the console, it looks like it can't load any of the files in the static folder. Heading directly to the link yields a 404 error, and it looks like the files are missing on the server side.
Here are the chrome errors from my development site:
If anyone has any advice it would be greatly appreciated.
Is it intended ? I'm adding them in header/footer.content but default css doesn't look great.
we have now in subtotal.html
data-bind="i18n: title"
class="mark"
scope="row cart-totals__row-label"
and we should move cart-totals__row-label class from scope to class attribute
I will fix it soon
Hello, I've successfully installed your theme. It's amazing. But I can't see the customer login icon. Is it normal? If so, can you please suggest how to enable it?
Thanks
there are not used icons in https://github.com/SnowdogApps/magento2-alpaca-theme/tree/develop/web/images/icons
dev-37746
Is it possible to disable the snowdog menu?
We are using an import based menu with the standard magento menu.
If I disable the Snowdog_Menu I get the following error:
Fatal error: Uncaught Error: Cannot instantiate interface Snowdog\Menu\Api\MenuRepositoryInterface in...
In short:
I want to use the normal Magento Menu
Thx in advance
I've decided to check out your alpaca theme for an ecommerce project after discovering the potential of SASS.
I am running M2.3.1 - The installation process is fine.
themes.json:
{
"alpaca": {
"src": "vendor/snowdog/theme-frontend-alpaca",
"dest": "pub/static/frontend/Snowdog/alpaca",
"locale": ["en_US"],
"modules": {
"Snowdog_Components": "vendor/snowdog/module-alpaca-components/components"
}
},
"light": {
"parent": "alpaca",
"src": "vendor/splys/theme-frontend-light",
"dest": "pub/static/frontend/splys/light",
"locale": ["nb_NO"],
"localeOverwrites": true,
"modules": {
"Snowdog_Components": "vendor/splys/module-light-components/components"
}
}
}
in /tools directory, running
gulp styles && gulp babel && gulp svg
Successfully compiles for both child and parent theme. I noticed that no vendor folder was created during the installation & compilation for splys
vendor-theme. The child content is found in pub/static etc, but not in /vendor.
Questions & problems:
gulp styles && gulp babel && gulp svg
everytime to reinitialize the style. Intended? Any practices to follow here?Can you spoonfeed me with a neat how-to, by answering these questions? An installation video on youtube + workflow from scratch would help a lot of people, including myself. I'm very eagered to get going here, so I hope you can do me and potential others this favour and also include some tips & tricks!
Reason I'm asking is that I feel the documentation provided was a little short and could've included a few examples for beginners such as myself.
Thank you for your hard work!
We have to consider what we can do with CMS block and CMS pages like header contact info, Homepage etc.
There is one link to check https://github.com/ctidigital/magento2-configurator
In .html files we have hardcoded text for example for aria-label etc attributes.
/Magento_Checkout/web/template/minicart/item/default.html
<a
data-bind="attr: {href: configure_url, title: $t('Edit item')}"
class="button button--icon minicart-product__button"
aria-label="edit product in your shopping cart"
>
We should move aria-label to data-bind="attr: {[here]}
and use $t method if available in specific file.
Hi,
When I update my magento to the last version (2.3.5-p1) the update will stop by an unknown package of snowdog:
- Installing snowdog/module-colibri-frontools (0.2.1): Cloning 3b48d83f8a
[RuntimeException]
Failed to clone https://github.com/SnowdogApps/magento2-colibri-frontools.git via https, ssh protocols, aborting.
- https://github.com/SnowdogApps/magento2-colibri-frontools.git
Cloning into '/path/to/magento2/vendor/snowdog/module-colibri-frontools'...
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/SnowdogApps/magento2-colibri-frontools.git/'
- [email protected]:SnowdogApps/magento2-colibri-frontools.git
Cloning into '/path/to/magento2/vendor/snowdog/module-colibri-frontools'...
ERROR: Repository not found.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
When I replace the snowdog/module-colibri-frontools in composer.json the update will be good.
"replace": {
"snowdog/module-colibri-frontools": "*"
}
To do on single order view:
I am not sure if it is a bug but, in developer mode there is a mode in Stores-> Settings-> Configuration-> Advanced -> Developer-> CSS Settings: Minify CSS Files. When it is enabled then Magento expects i.e. (pub/static/frontend/Snowdog/alpaca/pl_PL/Magento_Checkout/) checkout.min.css instead of checkout.css or (pub/static/frontend/Snowdog/alpaca/pl_PL/css) styles.min.css instead of styles.css.
I worked around it making the copy of existing file with the correct name with ".min.".
I have this error in console:
Failed to load resource: the server responded with a status of 404 () " /snownav.php"
How can I solve it?
Where can I find it?
Magento CE 2.2.6
Clean Alpaca Theme
Breadcrumbs are not displaying as expected on the product detail page. Since Magento CE 2.2.4 there is a separate breadcrumbs file in Magento_Catalog/templates/product/breadcrumbs.phtml. We probably need to override this file with our own styled version. See this issue magento/magento2#15490
Default Magento reCaptcha is not accessible, we should implement google reCaptcha:
https://developers.google.com/recaptcha/
https://github.com/magespecialist/m2-MSP_ReCaptcha
https://github.com/magento/magespecialist_ReCaptcha/
We should add this in theme dependencies and implement on demo page.
Missing tab-content in product-view
Preview: www.alpaca-ce-demo.snowdog.pro/hera-pullover-hoodie.html
Internal: Internal: #49294 /
There are places were we use in html attr escapeHtml
instead of escapeQuotes (M 2.1) or escapeHtmlAttr (> m2.2) or where we don't use any escape methods. The same for url etc.
However which method should be used vary depending on Magento version but I think we should support from some release > M2.2 and keep support for M2.1 on some release branch.
What method to use and when explained here:
https://devdocs.magento.com/guides/v2.3/frontend-dev-guide/templates/template-security.html
For M 2.1: https://devdocs.magento.com/guides/v2.1/frontend-dev-guide/templates/template-security.html
Footer links move from phtml (vendor/snowdog/theme-frontend-alpaca/Magento_Theme/templates/footer/footer-links.phtml
) to cms menu (snowdog/module-menu
) after resolving issue concerning overwriting templates by menu id
Hi, thanks for the great work. I can see that Cypress E2E tests have reasonable coverage in the open PR, and are a good base. Unfortunately, all data-testid attributes are available only on develop branch. Do you plan to release those or some easy way to get only data-testid related commits and merge them in a custom theme?
There is a problem with the reviews summary calculation because the name of the rating input field is using an incorrect variable
1 exception(s):
Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'referenceBlock', attribute 'class': The attribute 'class' is not allowed.
Line: 1142
Element 'referenceBlock', attribute 'cacheable': The attribute 'cacheable' is not allowed.
Line: 1142
Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'referenceBlock', attribute 'class': The attribute 'class' is not allowed.
Line: 1142
Element 'referenceBlock', attribute 'cacheable': The attribute 'cacheable' is not allowed.
Line: 1142
This module might help - https://github.com/ctidigital/magento2-configurator
Hello - there was a reply to an issue in the Snowdog Blank SASS theme git repo which suggested that a child theme for a magento installation using frontools should go into /vendor/{client}/{client-theme}. However, when doing that, Magento wasn't able to find my theme in the admin panel. I moved it to /app/design/frontend/{client}/{client-theme}, and that worked.
Running "gulp styles && gulp babel && gulp svg" doesn't throw any errors, but I'm not sure if it's really accessing the correct location for my child theme.
Before I go forward I just want to make sure that my /dev/tools/frontend/config/themes.json is correct for the child theme's "src" variable. Should it reference vendor/ or should it reference app/design/frontend/ ? As you know, the README for this project defines the default themes.json for a child theme with alpaca as parent such that "src" for the child references vendor/ - which didn't let Magento find it.
eg,
"src": "vendor/{vendor-name}/theme-frontend-{theme-name}",
or
"src": "app/design/frontend/{vendor-name}/theme-frontend-{theme-name}",
Did something change in Magento that caused it to stop loading themes in the vendor/ folder? or have I mis-configured some other file?
This theme looks great, but I've been struggling to try and get it to run. I successfully followed the installation steps and ran all the commands, and went in and changed the theme to Alpaca. Unfortunately, when you visit the home page, it's missing all the CSS and JS. When I check the console, it looks like it can't load any of the files in the static folder. Heading directly to those links yields a 404 error, and it looks like the files are missing on the server side.
I tried re-running gulp styles in hopes of generating those files, but to no avail. Here are the chrome errors from my development site:
(index):1 Refused to apply style from 'http://store.kidzkorner.cf/pub/static/version1560259397/frontend/Snowdog/alpaca/en_US/css/styles.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
/pub/static/version1560259397/frontend/Snowdog/alpaca/en_US//images/icons-sprite.svg#heart:1 Failed to load resource: the server responded with a status of 404 (Not Found)
(index):1 Refused to apply style from 'http://store.kidzkorner.cf/pub/static/version1560259397/frontend/Snowdog/alpaca/en_US/css/styles.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
/pub/static/version1560259397/frontend/Snowdog/alpaca/en_US/images/icons-sprite.svg#close:1 Failed to load resource: the server responded with a status of 404 (Not Found)
jquery-migrate.js:23 JQMIGRATE: Migrate is installed with logging active, version 1.4.1
VM14:1 GET http://store.kidzkorner.cf/pub/static/version1560259397/frontend/Snowdog/alpaca/en_US/js-translation.json 404 (Not Found)
http://store.kidzkorner.cf/pub/static/version1560259397/frontend/Snowdog/alpaca/en_US/js-translation.json HTTP status: 404
at XMLHttpRequest.xhr.onreadystatechange (text.js:115)
If anyone has any advice it would be greatly appreciated.
It looks like Special Price markup is not matching the component https://alpaca-components-staging.herokuapp.com/components/detail/price--with-special-price.html.
I have Vanila Magento 2.3 Open Source and Alpaca installed. Nothing else.
<div class="catalog-grid-item__price">
<div class="price">
<span class="price__value">
<div class="price-box price-final_price" data-role="priceBox" data-product-id="1" data-price-box="product-id-1">
<span class="special-price">
<span class="price-container price-final_price tax weee">
<span class="price-label">Special Price</span>
<span id="product-price-1" data-price-amount="25" data-price-type="finalPrice" class="price-wrapper "><span class="price">£25.00</span></span>
</span>
</span>
<span class="old-price">
<span class="price-container price-final_price tax weee">
<span class="price-label">Regular Price</span>
<span id="old-price-1" data-price-amount="37.99" data-price-type="oldPrice" class="price-wrapper "><span class="price">£37.99</span></span>
</span>
</span>
</div> </span>
</div>
</div>
Hello, I've had the following message when trying to install with composer :
Could not find a matching version of package snowdog/alpaca-packages
Did I miss something?
Issue:
In customer/account/edit page, after select "change password" and fill all input fields. Click "save" button.
"You saved the account information" success message shows, but the password not changed.
Possible Reason:
check Magento_Customer/templates/form/edit.phtml
commits 202be6b and ff6c51b
checkbox name changed from "change_password" to "account_update", value changed from "1" to "changePassword".
magento/module-customer/Controller/Account/EditPost.php line 258
changeCustomerPassword function will check
if ($this->getRequest()->getParam('change_password'))
Can you provide insight? I see documents and forum posts everywhere, but I am starting a new project and evaluating Magento-base theme vs alpaca vs theme-blank-sass .. Can you explain recommended use? Do these all use frontools and replace Magento-recommended CLI commands? or has magento implemented? I see they have selectors and things now?
FYI - I am using Docker with a PHP container containing the node, gulp, gulp-cli and bower components necessary to start and can adapt that if necessary. I had theme-blank-sass working and then noticed alpaca was maybe more modern or a rewrite/re-develop?
Also, could you provide link to or maybe mention here the appropriate commands for requiring the theme/components/tools and also standard development workflow using commands?
Hello, im novice, would like know how to install this theme with components.. Thanks!
Hello, I am trying to use your alpaca theme because I am frustrated with Magento's frontend scheme using LESS. I don't have a problem with LESS, but the structure is confusing.
I am at the step "Install Frontools dependecies and setup config files cd vendor/snowdog/frontools && yarn && gulp setup"
Yarn barfs on my node.js version 10... I am hosted at Nexcess so don't have access to modify the server, though I can request version 12... is this necessary or can I just change the version requirement in /vendor/snowdog/frontools/.node-version ?
Magento 2.3.3 Commerce, Alpaca theme 1.3.1, Elasticsearch 6, Magento Sample data installed, visiting any category page will results in the message - "We can't find products matching the selection." shown in the products list space. The same as if no products are available.
With the same product setup but with mysql as a search engine products load successfully.
I have tracked down the issue to:
<!-- vendor/snowdog/theme-frontend-alpaca/Magento_Catalog/layout/catalog_category_view.xml:21 -->
<!-- Moved blocks -->
<move element="div.sidebar.main" destination="columns" before="main"/>
Moving Layered navigation before the product list causes the empty product collection. If I comment this line the product collection loads fine.
On Mangeto 2.3 on the product page, related products' images do not appear. Probably there is a problem with styles.
On Magento 2.3.0, when configurable products are set up with different option prices, they do not seem to be reloaded in the Catalog List upon selecting a swatch option
Header in readme says "Snowog" instead of "Snowdog":
Hey Guys,
i'm planning to use the alpace theme as base theme for some of our projects.
This is looking very good.
Few questions tho, is there some documentation available how to set this up in magento 2?
Problems/questions I have now are:
Cheers,
Hi, after following your instructions to install this theme, I get the following error when I activate the theme in Magento. Any help would be appreciated.
2019/01/12 02:55:41 [error] 12991#0: *593 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Cannot instantiate interface Snowdog\Menu\Api\MenuRepositoryInterface in /var/www/magento.xxxxxxxxxxxxxxxxx.com/htdocs/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php:50
Stack trace:
#0 /var/www/magento.xxxxxxxxxxxxxxxxx.com/htdocs/vendor/magento/framework/ObjectManager/ObjectManager.php(70): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Snowdog\\Menu\\Ap...')
#1 /var/www/magento.xxxxxxxxxxxxxxxxx.com/htdocs/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(160): Magento\Framework\ObjectManager\ObjectManager->get('Snowdog\\Menu\\Ap...')
#2 /var/www/magento.xxxxxxxxxxxxxxxxx.com/htdocs/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(246): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'Snowdog\\Menu\\Ap...', NULL, 'menuRepository', 'Snowdog\\Menu\\Bl...')
#3 /var/www/magento.xxxxxxxxxxxxxxxxx.com/htdocs/vendor/magento/framework/ObjectManager/Factory/D" while reading response header from upstream, client: xx.xx.xx.xx, server: magento.xxxxxxxxxxxxxxxxx.com, request: "GET / HTTP/2.0", upstream: "fastcgi://127.0.0.1:9090", host: "magento.xxxxxxxxxxxxxxxxx.com"
Add info which browsers we are supporting in this theme. Add this info to reamde
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.