|
@tecoad
Unfortunately, we can’t confirm none of your bugs. Please, inform us, when you go live, or provide an accessible testing page. Until then we’ll cease from investigating them.
The SVG buttons work fine on all browsers for us.
About the blog problem, please make sure you don’t have saved scopes with greater priority:
System > Stories > Articles Listing
System > Stories > Articles by Tag
BR,
ThemeBurn team
|
|
|
@TB Support
Live Search doesnt work, show this error:
Notice: Undefined index: quantity in /home/shishalo/public_html/vqmod/vqcache/vq2-system_modification_catalog_controller_module_latest
.php on line 74Notice: Undefined index: stock_status_id in /home/shishalo/public_html
/vqmod/vqcache/vq2-system_modification_catalog_controller_module_latest.php on line 75Notice
: Undefined index: quantity in /home/shishalo/public_html/vqmod/vqcache/vq2-system_modification_catalog_controller_module_latest
.php on line 76Notice: Undefined index: stock_status_id in /home/shishalo/public_html
/vqmod/vqcache/vq2-system_modification_catalog_controller_module_latest.php on line 76
|
|
|
Regarding to the bug in the html block
When adding this:
<img src="test.jpg" alt="test" height="42" width="42">
<script>console.log("hello world");</script>
After saving, logging out and relogging we get this result in the block:
<span class="image-holder" style="max-width: 42px;"><span style="padding-top: 100%;"><img src="test.jpg" alt="test" height="42" width="42" style="margin-top: -100%;" class=" lazyload"/></span></span><script><![CDATA[console.log("hello world");]]></script>
The javascript is blocked and some new lazyload stuff.
Can you confirm this bug?
Best regards, Ultimatia
-
This reply was modified 3000 days ago by
 ultimatia.
|
|
|
@ultimatia – confirmed, will be fixed in the next release. For now, do not use javascript inside the html block.
|
|
|
@TB Support
My bad, I was not aware of the the (System > Stories > Articles Listing). Sorry.
I am updating my online demo to beta 11. Meanwhile, it made this video to show you the font bug issue:
https://www.dropbox.com/s/1eo1dz03egpz4uy/font-bugs.mov?dl=0
|
|
|
@tecoad
Can you please expand the font-size value (16) under the “Computed” tab?
Can you please expand the font-size value for the parent element? It is the one that has the actual font-size assigned to.
Thanks,
ThemeBurn team
|
|
|
@TB Support
Just a suggestion…
Something that I would find extremely useful (perhaps others may feel the same) would be a way to save a block style that has been customized in the builder as a preset style that can be applied later on by the user. I believe this would be a tremendous time saver for many people.
I understand you have the preset builder which is GREAT but if you added that ability, I think the preset feature would be even more rounded out!
|
|
|
@TB Support,
Update: the heading issue has been caused by some custom css. I fixed that on my css. Sorry for this.
-
This reply was modified 2999 days ago by
 tecoad.
|
|
|
BETA 12 released.
All of the reported issues have been fixed and the shared folder has been updated. Just re-upload and overwrite the existing files.
After the upgrade you need to re-save Theme Settings -> System in order to prevent some notices.
@tecoad – we cannot figure out the SVG issue for now.
Regards,
ThemeBurn team
|
|
|
@TB Support:
Great!
I’ll investigate further on the SVG issue later today…
|
|
|
Good work!
No important bugs so far.
- Live search working great
- fontrendering issue looks fixed in Chrome in v49.x
- Javascript/ img issue is fixed.
Br.
|
|
|
Live Search – doesn’t show image (though turned on in settings), shows hints (though turned off in settings).
|
|
|
Also in my case SEO extension – when I try to generate product urls it loaded for half an hour and nothing happened.
|
|
|
@TB Support:
About the close modal font rendering on Chrome, just found out:
Somehow, the icon has not been recognised as an FontAwesome element.
If I manually replace
<a class="close" href="javascript:;" data-dismiss="modal">
to
<a class="close" href="javascript:;" data-dismiss="modal" style="font-family: FontAwesome;">
it works fine.
Wouldn’t be the case to assign fontawesome to the close class?
|
|
