Mr.Andreius
Mr.Andreius
these errors occurred when I moved the admin node-red to a new URL ( botsite.com/admin ) and disappeared when returned > big update I hope there will be an opportunity...
yes, the idea was to use a few bots, but it didn't work
> Got that one.. I found a solution where node-red suppose to be accessed from outside as https and not 127.0.0.1 allowing telegram to know.. Anyway I got my fixed...
+ my cent add the first step of verifying the version of WordPress as it is done in Twenty Seventeen
data-top-anchor="main-content:top" data-btm-anchor="products:bottom" replase "main-content:top" to products:top ?
try changing in https://github.com/olefredrik/FoundationPress/blob/c078fc39a5f3fe428e8a99ad365c1c435c367657/template-parts/featured-image.php#L5 `
@nitrokevin Try restarting the module after loading the page something like ` // Fire on document ready. $( document ).ready( function() { var frame_image = $('#frame-image'); var imageFrame = new...
file rename class-foundationpress-mobile-walker.php to class-theme-name-mobile-walker.php
Please add to `// Open the unordered list. ` the ability to specify your own class list_class something like that ``
found another place where the theme name is written incorrectly composer.json `"autoload" : { "psr-4" : { "Themename\\" : "app/" // need ThemeName } },` this may then again cause...