We're having several issue upgrading and using Layla. I tried to contact you via email and go nesponse.
if we upgrade then the header breaks using the svg and custom.css no longer functions.
with the version we have now ( 1.0.8 ) we have no mobile menu.
How can this be resolved?
- N6REJ
- Commercial Templates
- Monday, 17 October 2022
- Subscribe via email
I just discovered I purchased the J3 template NOT the j4.
How can I get the proper j4 version?
How can I get the proper j4 version?
- more than a month ago
- Commercial Templates
- # 1
Hello
I have just updated your purchase to the Joomla 4 version of the template which should be now available for you to download via your Profile -> Template Downloads.
Ciaran
I have just updated your purchase to the Joomla 4 version of the template which should be now available for you to download via your Profile -> Template Downloads.
Ciaran
- more than a month ago
- Commercial Templates
- # 2
That solved the J4 download issue, but we are having SEVERAL issues with custom.css and ancient J! remainder files from the quickstart. Whats the best way this can be handled?
For example, we can't have custom.css in /media/css as its not recognized by the template.
The latest issue, is we started a clean slate site and started slowly migrating everything over ( huge job ) and we're seeing these errors in console...
UPDATE: using https solved the above issue but I don't know if thats correct behavior or not.
But these are just 2 of many many issues.
For example, we can't have custom.css in /media/css as its not recognized by the template.
The latest issue, is we started a clean slate site and started slowly migrating everything over ( huge job ) and we're seeing these errors in console...
The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead. See https://www.w3.org/TR/powerful-features/#potentially-trustworthy-origin and https://html.spec.whatwg.org/#the-cross-origin-opener-policy-header.
UPDATE: using https solved the above issue but I don't know if thats correct behavior or not.
Refused to apply style from 'http://new.bearsampp.com/index.php' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
But these are just 2 of many many issues.
- more than a month ago
- Commercial Templates
- # 3
Hello
May I suggest sending temporary administration access to your Joomla installation to info@joomla51.com and we will examine this issue further. For our reference please paste a link to this post in your email.
Ciaran
May I suggest sending temporary administration access to your Joomla installation to info@joomla51.com and we will examine this issue further. For our reference please paste a link to this post in your email.
Ciaran
- more than a month ago
- Commercial Templates
- # 4
Thank you
I notice you are using version 1.0.7 of the Layla template. Could I ask you to update your template to the current version (1.1.7) which should be available within your Jooml51 template downloads.
Regarding your CORS issue, deleting all cache and application data for this site from your browser should resolve the issue. On our initial loading of your site, these issues do not occur.
Ciaran
I notice you are using version 1.0.7 of the Layla template. Could I ask you to update your template to the current version (1.1.7) which should be available within your Jooml51 template downloads.
Regarding your CORS issue, deleting all cache and application data for this site from your browser should resolve the issue. On our initial loading of your site, these issues do not occur.
Ciaran
- more than a month ago
- Commercial Templates
- # 5
I've updated the template but your mistaken in that the core issues are browser related. They are 100% related to using the quickstart.
We've installed the template on a test site without using the quickstart and none of the core issues exist.
Looking at the database there are lots of extensions we've never used that exist and plenty of invalid entries.
We've tested with multiple users on multiple browsers. The results are the same.
We've installed the template on a test site without using the quickstart and none of the core issues exist.
Looking at the database there are lots of extensions we've never used that exist and plenty of invalid entries.
We've tested with multiple users on multiple browsers. The results are the same.
- more than a month ago
- Commercial Templates
- # 6
- Page :
- 1
There are no replies made for this post yet.
Be one of the first to reply to this post!
Be one of the first to reply to this post!
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »