6 months since this was updated? Is this no longer supported??
Looking at using theme Spasalon with Webriti Companion. Not much point if neither is supported anymore!
I was sent an email saying that my website has a critical error from Webriti Companion
plugin for the theme Dream Spa. I tried fixing it by updating. Now it says Webriti fails to load and I can’t get my homepage to show anything but the intro image and the News section which can only be viewed on my dashboard. When I go to my website when I’m not logged in it still shows my website as down and says ip address not found in chrome or insecure in mozilla with the maintenance page.
On “Service Settings” page and “Project Settings” page stand: Lorem Ipsum
Orci varius natoque penatibus et magnis.
i can’t edit this text?
]]>With or without this companion, I see no difference on my WP installation.
Any help or should I step forward to another theme?
]]>Webriti Companion のエラーです。
ダッシュボード→ツール→サイトヘルスでのエラーです。
バックグラウンドの更新が想定道りに動作していません。
×エラー プラグインは wp_version_check() を無効化してアップデートを防ぎました。
Webriti Companionプラグインを無効化するとエラーは出ませんでした、対処方法を教えてください。テーマはWallstreetです。
The site is in safe mode and this is the message on Plugins page:
Tiedoston /home3/kalliosydan/public_html/wp-content/plugins/webriti-companion/inc/spasalon/sections/spasalon-features-section.php rivill? 3 havaittiin virhe lajia E_ERROR. Virheviesti: Uncaught Error: Call to undefined function spasalon_default_data() in /home3/kalliosydan/public_html/wp-content/plugins/webriti-companion/inc/spasalon/sections/spasalon-features-section.php:3 Stack trace: #0 /home3/kalliosydan/public_html/wp-content/plugins/webriti-companion/webriti-companion.php(53): require_once() #1 /home3/kalliosydan/public_html/wp-includes/class-wp-hook.php(287): webriti_companion_activate(”) #2 /home3/kalliosydan/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array) #3 /home3/kalliosydan/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #4 /home3/kalliosydan/public_html/wp-settings.php(540): do_action(‘init’) #5 /home3/kalliosydan/public_html/wp-config.php(101): require_once(‘/home3/kalliosy…’) #6 /home3/kalliosydan/public_html/wp-load.php(37): require_once(‘/home3/kalliosy…’) #7 /home3/kalliosydan/public_html/wp-admin/admin.php(34): require_once(‘/home3/kalliosy…’) #8 /home3/kalliosydan/public_html/wp-admin/plugins.php(10): require_
I’m using the Mambo theme.
About a week ago there was some kind of update and the Webriti plugin installed itself.
It has messed up the image on my slider – the top and bottom of the image is cut off.
I would like the whole image to display properly as it did before the update.
Could you help me please?
Many thanks
The Plugin produces repeatedly header errors on an actual wordpress installation (Hoster: ionos.de). Deactivate it solves the problem. Website: Procreda.org, PHP 7.2
]]>Hi,
after updating Webriti Companion plugin to the 1.5/1.6 version, the sitemap does not work anymore and shows the following error:
This page contains the following errors:
error on line 1 at column 10: XML declaration allowed only at the start of the document
Below is a rendering of the page up to the first error.
If I install the 1.4 version again there’s no problem. I use latest version of WordPress and the latest version of the Quality theme.
]]>Hi,
Using WP 5.1.1 with theme “Quality”, I can not add any projects to my home page. I tried to create new pages as stated in the documentation, but the portfolio template is not electable as a template for the new page.
Also editing the portfolio from within Customizer does not work, and default portfolio items are still shown form your plugin.
Please help! Thanks in advance and kind regards,
Jack
When using this plugin and the Quality theme with a custom child theme ‘Service settings’, and ‘Project settings’ don’t appear in customizer.
I have disabled all other plugins. I have stripped the custom child theme of all functions customization and it is essentially a child theme placeholder. The options are available when I switch to the base Quality theme but not when switching to my custom child theme.
]]>