No unresolved topics found
Wordpress Mail: Um deine Website zu schützen, läuft dieser Link in 1 Tag ab. Aber keine Sorge: Ein neuer Link…
Hi Janos, thanks for your interest in purchasing a Billy PRO license. Basic multilingual support has been integrated in the…
The issue has been resolved in the latest version v1.8.1!
Short remark: While chatting with Peter about this issue we found out that there is a compatibility issue with another…
1 blocks boilerplate bootstrap countup development gutenberg headless-cms jquery JS lts material design npm plugin plus polymer reactjs sass starter support them.es+ theme tutorial VanillaJS wordpress wp-api
Issues or problems related to them.es products.
Hallo Zusammen, bei der neuen Version erhalte ich folgende Mledung bei der Aktivierung: Es gab einen kritischen Fehler auf dieser […]
Hallo Zusammen,
bei der neuen Version erhalte ich folgende Mledung bei der Aktivierung:
Es gab einen kritischen Fehler auf dieser Website. Prüfe bitte den Posteingang deines Website-Administrators auf Anweisungen. Wenn du weiterhin Probleme hast, wende dich bitte an die Support-Foren.
Des Weiteren habe ich leider meinen Aktivierungsschlüssel nicht mehr.
Gruß
Peter
WordPress Mail:
Um deine Website zu schützen, läuft dieser Link in 1 Tag ab. Aber keine Sorge: Ein neuer Link wird dir per E-Mail zugeschickt, wenn der Fehler nach Ablauf der Frist erneut auftritt. Wenn du Hilfe bei diesem Problem suchst, wirst du möglicherweise nach einigen der folgenden Informationen gefragt: WordPress-Version 6.8.3 Aktives Theme: Coachify (Version 1.1.5) Aktuelles Plugin: Billy (Pro) (Version 2.0.0) PHP-Version 8.4.14 Fehler-Details ============== Ein Fehler vom Typ E_ERROR wurde in der Zeile 124 der Datei /homepages/10/d4294976617/htdocs/waldbaden-exkursionen/wp-content/plugins/billy-pro/billy-pro.php verursacht. Fehlermeldung: Uncaught TypeError: billy_pro_output_block_value(): Return value must be of type string, null returned in /homepages/10/d4294976617/htdocs/waldbaden-exkursionen/wp-content/plugins/billy-pro/billy-pro.php:124 Stack trace: #0 /homepages/10/d4294976617/htdocs/waldbaden-exkursionen/wp-content/plugins/billy-pro/inc/class-admin.php(266): billy_pro_output_block_value() #1 /homepages/10/d4294976617/htdocs/waldbaden-exkursionen/wp-content/plugins/billy-pro/inc/class-admin.php(331): Billy_Pro_Admin->wp_dashboard_widget_body_pro() #2 /homepages/10/d4294976617/htdocs/waldbaden-exkursionen/wp-admin/includes/template.php(1456): Billy_Pro_Admin->wp_dashboard_widget_pro() #3 /homepages/10/d4294976617/htdocs/waldbaden-exkursionen/wp-admin/includes/dashboard.php(274): do_meta_boxes() #4 /homepages/10/d4294976617/htdocs/waldbaden-exkursionen/wp-admin/index.php(204): wp_dashboard() #5 {main} thrown
Thanks for reporting this issue, Peter. As confirmed via email, a v2.0.1 bugfix release has been published in the morning.
All available license keys can be looked up in your them.es account under https://them.es/account/
Hallo Zusammen, heute kam ein Update von Billy Pro. Nach der Akzualisierung kam sofort ein schwerwiegender Datenbakfehler. Durch die Deaktivierung […]
Hallo Zusammen,
heute kam ein Update von Billy Pro.
Nach der Akzualisierung kam sofort ein schwerwiegender Datenbakfehler.
Durch die Deaktivierung aller PlugIns konnte ich wieder auf WordPress zugreifen.
Nachdem ich alle PlugIns wieder aktiviert hatte (außer Billy Pro) lief meine Homepage wieder.
Nach der Aktivierung von Billy Pro hatte ich allerdings wieder den Fehler.
Gruß
Peter
Short remark: While chatting with Peter about this issue we found out that there is a compatibility issue with another plugin “Amelia Booking” where a (composer) dependency clashes with the same one used in Billy PRO.
The dependencies of Billy PRO need to be reorganized to allow multiple versions of libraries without conflict.
The issue has been resolved in the latest version v1.8.1!
After Update from woocommerce.8.5.2 to woocommerce.8.6 the_content is not load for people who are not logged in. Seems like comes […]
After Update from woocommerce.8.5.2 to woocommerce.8.6 the_content is not load for people who are not logged in.
Seems like comes from a wp core function $content = apply_filters( ‘the_content’, $content ); in the the_content function.
When i rollback its works. I also have try it with a fresh generatet version of Starter Theme, same.
With other themes its working i had try till twentynineteen.
Theres no error i have investet some time but found not a reson why its now not working
Rollback to 8.6 RC its working so the problem must be from RC to final
Hi stefanbd,
thanks for getting in touch. You’re right – there seems to be a bug in WooCommerce v8.6.0 (see https://github.com/woocommerce/woocommerce/issues/44679) which already has been been fixed in v8.6.1, released yesterday.
Could you confirm that upgrading WooCommerce to the latest version makes the_content() accessible to unauthenticated users again?
Hi thanks for the hint, after update to 8.61 its working again.
I was think its a problem with your theme because i have try themes from store and they hadnt the problem.
Hello, I installed the starter spa theme and am having trouble with the navigation menu. In wp-admin, I created the […]
Hello, I installed the starter spa theme and am having trouble with the navigation menu. In wp-admin, I created the menu items with sub menu item, but they are not nested. Also, the menu is not scrollable so you cant see the menu items that are “below the fold”. Not sure if the theme even supports this, so I thought I would ask. Thanks!
Using wordpress 5.2. Ive attached screenshots of the admin menu builder and a screenshot of the websites homescreen.
Hi jerm!
Unfortunately nested menus are not supported in the Polymer Starter Kit which has been used as basis for the theme.
For larger sites which need support for submenus it would be better to use the Bootstrap Starter Theme.
Thanks for informing us about the sidebar scrolling issue. This has been fixed in the latest release: https://them.es/starter-spa
Awesome, thanks for the reply!
I will download the latest version and give it a try. Thanks for the reply!
~Jerm
Thanks for reporting this issue, Peter. As confirmed via email, a v2.0.1 bugfix release has been published in the morning.…