Plugin Author
WPSOLR
(@wpsolr)
This error occurs because the twig_cycle() function is being declared twice. It seems that both the WP RSS Aggregator plugin and WPSOLR plugin are using the Twig templating library, and each is loading a different version or a conflicting part of Twig, leading to a function redeclaration.
WPSOLR always try to use the latest external library version, which includes the latest security fixes.
Here Twig 3.14.0 (2024-09-09)
We have seen the conflict, but we cannot uninstall wp rss. Could you suggest how we can fix this?
Thank you!
Plugin Author
WPSOLR
(@wpsolr)
You might edit the Twig file in one of the plugins to wrap the twig_cycle() function in a conditional to prevent redeclaration.
In the WPSOLR plugin, open the file:
/home/[notdisclosed]/public_html/wp-content/plugins/wpsolr-free/wpsolr/core/vendor/twig/twig/src/Resources/core.php
Wrap the twig_cycle() function definition with a check to see if it’s already been declared:
if (!function_exists('twig_cycle')) { function twig_cycle() { // function code here } }
But the same issue on other methods could also happen.
Plugin Author
WPSOLR
(@wpsolr)
I installed the WP RSS Aggregator plugin, and it appears to use a five-year-old version of Twig (v1.41.0) from Twig’s repository.
Unfortunately, I don’t believe we can run easily both Twig versions simultaneously without conflicts.
Thank you very much for investigating further our issue. We cannot modify that function because on the next update the modification would be lost, so we already have decided to uninstall wp rss plugin and move the feeds to another plugin. We need more WP Solr than wp rss, because we want to improve the search engine and we contemplate to install weaviate or vespa, but we not sure which one yet.
Thanks!
Plugin Author
WPSOLR
(@wpsolr)
Nice.
Vespa.ai offers multi-stage hybrid ranking and supports ColBERT models, which are very trendy these days.
With Weaviate, you will get ready-to-use multimodal models with local embedders, like CLIP.
We have a lot of documentation to read on regard, first of all 🙂 The Weaviate has QA integrated which can be used out-of-the box with WP Solr, but we have to figure it out how to display it in an overlay on post pages for summarizing the posts on demand, among a lot of other things, like using jina-embeddings-v-3 and its segmenter API for chunking and embedding or voyage-law-2 (because we will have legal content on the website in romanian language), just to mention a few.
Thanks a lot again!
@wpsolr I would like to ask an off-topic question related to Weaviate installation in production environment, if it’s allowed.
In WPSolr documentation it is recommended to install Weaviate using Docker, while in the Weaviate documentation it is recommended to install it using Docker only for testing purposes. For production env. they recommend to use Kubernetes. It would be a problem if we will install Weaviate using Docket in production env., how we should proceed?
thx!
Plugin Author
WPSOLR
(@wpsolr)
Using Kubernetes gives you scalability and fault resistance, as data and queries are distributed across nodes.
But Docker is great. The plugin description has a link to install Weaviate on Docker.
Hi,
we considered to use WPSolr with Weaviate Cloud instead of locally installing it, but in WPSolr plugin it is not possible to use a cloud instace of Weaviate. How this can be done?
Thanks,
