vasta88

I agree, the issue is when asking to index custom fields which include post objects. We use Relevanssi on over 50 of our sites, but we also rely heavily on Advanced Custom Fields to build our themes. We often store post objects in some of our fields, and so the Relevanssi search can’t index using all or visible, and we have too many fields to name each one individually.

Unfortunately, unless this issue can be fixed we’ll be forced to switch to a new search optimizing plugin. We’ve had great experiences with Relevanssi in the past and we’re sorry to have to do it. Please let us know if a future update solves this issue.

Actually I’ve found that the new compiler used in version 1.8 has a problem with multi-line comments sometimes. We get a similar error (it acts like there’s a missing closing comment when there isn’t), but on the earlier versions of the plugin we have no problems. For example, the following code produces an error:

/*! #Fonts and Colors *//*
================================================== */
@primary-font: ‘Lato’, sans-serif;
@secondary-font: ‘Cardo’, serif;

//blues
@header-blue: #66939c;

Me too, as well as another developer in my area.
My code worked fine until I updated the plugin. I ended up reverting to an older version of the plugin, which fixed things for me.

Error Log showed the following:
PHP Fatal error: Uncaught exception ‘Less_Exception_Chunk’ with message ‘ParseError: unmatched /* in layout.less on line 29, column 52\n27| \t\n28| /*! #Fonts and Colors *//*\n29| ================================================== */\n30| @primary-font: ‘Lato’, sans-serif;\n31| @secondary-font: ‘Cardo’, serif;\n32| ‘ in /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php:535\nStack trace:\n#0 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php(474): Less_Parser->GetRules(‘/nas/wp/www/clu…’)\n#1 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php(346): Less_Parser->_parse(‘/nas/wp/www/clu…’)\n#2 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lessc.inc.php(147): Less_Parser->parseFile(‘/nas/wp/www/clu…’)\n#3 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lessc.inc.php(225): lessc-> in /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php on line 535

I am actually having almost the same problem with version 1.8.0
I have several comments with /*! stuff here */ and they seem to be causing parse errors, though they didn’t on the old versions. Is this something that is fixable, or should I just go change my comment structure for the relevant sites?

Error Log shows the following:
PHP Fatal error: Uncaught exception ‘Less_Exception_Chunk’ with message ‘ParseError: unmatched /* in layout.less on line 29, column 52\n27| \t\n28| /*! #Fonts and Colors *//*\n29| ================================================== */\n30| @primary-font: ‘Lato’, sans-serif;\n31| @secondary-font: ‘Cardo’, serif;\n32| ‘ in /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php:535\nStack trace:\n#0 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php(474): Less_Parser->GetRules(‘/nas/wp/www/clu…’)\n#1 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php(346): Less_Parser->_parse(‘/nas/wp/www/clu…’)\n#2 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lessc.inc.php(147): Less_Parser->parseFile(‘/nas/wp/www/clu…’)\n#3 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lessc.inc.php(225): lessc-> in /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php on line 535