|
Ah, thanks! Indeed, 2 files from an extension had a BOM inside. Need to inform the developer about it.
Regarding the system widget elements on the product page: So I can easily customize every little think of the appearance? How does that work? Where is the difference between the block Description and Product.description?
|
|
|
@TB Support
On Safari, the last item of the first row in products listing, special features, go down, i dont know why only in Safari.
You can check here: http://www.hispacachimba.es
|
|
|
@TB Support
As @Axanne previously stated, I really like the idea of having the ability to modify every component on the product page with the new widgets for:
Product
Product.thumb
Product.title
Product.description
Product.price
Product.tax
etc…
However, I was curious if you could explain how to use them? I have not been able to apply any of them with any success. They seem to apply to the layout fine, but when you go to the front end, nothing is displayed in those slots.
Thanks in advance!
|
|
|
@axanne, @TXVaporGuy – the additional product widgets, that have dot inside the name are indeed a bug. Sorry, our bad. You can’t use them, they will disappear in the next release.
@adimpacto – update to beta.9, it includes the Safari fix.
Regards,
ThemeBurn team
|
|
|
@TB Support
I cant make work facebook comments in Stories article, maybe i need to put some code in SOCIAL SHARE textbox inside configuration?
|
|
|
@TB Support
Something I have found to be quite burdensome is when you add a menu to the page builder and set the Level 1 menu style to “none”, every time you go back to modify anything on that block’s style, it resets that menu style to “hidden”. This can be quite a pain when working with multiple menus within a single layout because resetting them all to “hidden” each time makes them not appear.
Which brings me to another question, why is there even a style for “hidden”? Seems that if someone didn’t want a menu to show, they could either disable the menu widget or simply remove it from that page builder position.
Feel free to chime back with suggestions or comments.
|
|
|
@TXVaporGuy
The reset of level 1 menu styles setting is definitely a bug. Thanks for reporting it!
About the use of the “hidden” value; the idea was to have an option that will help you reuse same menu sets for different positions. I will give you a quick example:
1) You have the following menu set:
Categories (url/anchor)
- Category lvl 1
- Category lvl 2
- Category lvl N
2) You insert the set as a horizontal navigation in the header; submenus (categories) are shown in a dropdown.
3) You want to insert the same set in the sidebar. You don’t need the level 1 anchor, as you only want a visible list of categories. Without the “hidden” style option, you had to create a new menu set.
Hope this makes the things a bit clearer 
BR,
ThemeBurn team
|
|
|
Hello
I was wondering if there is any clue on the
Notice: Undefined property: Loader::$config
and
Fatal error: Call to a member function get() on a non-object
in relation to the error/not_found.tpl appearing in cart/checkout since upgrading to Beta9?
|
|
|
@TB Support
Thanks for clearing that up!
Perhaps you can shine some light on another question I had about the theme feature for deferring JS. We are trying to use a module on our site and it calls JS for the functionality. When the theme setting has defer JS selected, the module does not work. When I turn off the defer JS setting, the module begins working. I know that this is related to where the JS is being inserted with VQMod or OCMod, but can you advise where we should insert the script in the header and footer to prevent it from being deferred?
Thanks!
|
|
|
@hotscotchbonnet – the Notice: Undefined property: Loader::$config error appears when you enable the default theme too. It is caused from an extension, called ‘Error pages monitor’ and is not related to BurnEngine.
@TXVaporGuy – we are very curious which extension has javscript problems with BurnEngine. We could advise you where to insert scripts, but we prefer to provide a general fix. Can you send us the extension ? Also do you still experience errors when you attempt to export with all options enabled ? We were unable to find your ftp credentials in order to test.
Regards,
ThemeBurn team
|
|
|
Sure thing @TB Support
If you don’t mind, please shoot me an email.
|
|
|
Hello TB support,
I installed a 2.1.0.2 Dutch language translation, only not all in the shop has been translated.
Do I have to edit the file theme.lang.php in folder: /public_html/catalog/language/english/BurnEngine
(I deleted English from backend, not files)
Or do I have to follow topic: http://support.themeburn.com/topic/localization-add-new-language
and create in dutch folder, new folder BurnEngine with files?
Other question, I use only built in fonts, where can I disable external Google fonts resources?
Thx,
Ray
-
This reply was modified 3008 days ago by
 spiruella.
|
|
|
@spiruella
If the theme lang file is missing for the active language, Pavilion is looking in the fallback folder (English). This means that, if you choose not to copy the file and translate it directly, it will work.
Nevertheless, it would be more neatly, if you follow the tutorial
BR,
ThemeBurn team
|
|
|
@TB Support
From BETA9:
Have you noticed the svg icon for closing product review modal is broken? Image..
|
|
|
BETA 10 released.
All of the reported issues have been fixed and the shared folder has been updated. Just re-upload and overwrite the existing files.
Before upgrading to Beta 10 you have to uninstall and delete the ‘advanced search’ extension. Just remove the BurnEngine/extensions/advanced_search folder. You can re-enable it after the upgrade.
After the upgrade you should re-save your cache settings in Theme Settings -> System. You may have to re-save the theme colors as well. Just enter the `BurnEngine panel -> Theme Settings -> Colors` and hit ‘Save colors’. This is needed if you experience ‘‘Color inheritance issue’ error notice after the upgrade.
If you continue to receive errors or notifications (you shouldn’t normally), you may need to re-install the BurnEngine module (just uninstall it and install it again from the OpenCart modules menu).
We really hope this is the last beta before the final release.
Regards,
ThemeBurn team
|
|
