adcgn

Thanks for the quick reply. Yes, that works now. However, it is not as convenient as expected. But that seems to be a Bricks issue. When I turn on the excerpt settings, I can still use the styling; otherwise, search terms are marked with <strong>.

User searches are still double-counted, which also seems to be a Bricks issue.

• This reply was modified 2 years, 2 months ago by adcgn.

I have the same problem. And I asked the Bricks support about it. They answer that the {post_excerpt} dynamic code uses $post->post_excerpt. But it only shows the original excerpt, not the amended Relevanssi one.

I tried to enable debugging but without luck. Enabling or disabling does not change anything. How is that supposed to work?

As an alternative, I enabled logging, and I can see that Relevanssi logs the user search with the appropriate search terms. However, each search is counted double, i.e., each search results in two logged searches with the same term.

Is there any option I could use to debug what is happening in the console or similar?

After some testing, I figured out that it works if I save the posts/pages again and clear the cache afterward. However, this is a tedious job for all posts. I moved from RankMath to Slim SEO and I imported all the settings which worked for all other fields except images. How can I fix that?

Thanks, that sounds good. Is there a rough timeline?

Gute Frage, die ich mir auch gerade gestellt habe. Das Design ist ein wenig altbacken und ist leider nicht voll responsiv. Wenn das in der Free Version nicht funktioniert, macht es für mich keinen Sinn auf die Pro Version zu wechseln.

After fiddling with a lot of options, I found the problem. It is not about this plugin! My WordPress runs on a Litespeed server, and that handles both inline and external JS code. The provided shortcode creates a JS snippet. Then Litespeed takes “care” of it, resulting in a missing code. Turning off the Litespeed optimizations for JS brings back the form.

I am unsure why this happens, but this solves the issue (which was never an issue of this plugin). Funny enough, it does affect the JS of the WP Mautic plugin only.

Hi @tsteur,

I use a managed WordPress Hosting. Meanwhile, I switched to the external hosting of Matomo and, thus, switched the plugins. That works without issues. For testing purposes, I installed the plugin again. Here are the details (I removed any unrelated stuff). I hope it helps.

# Matomo

* Matomo Pluginversion: 4.0.4
* Config existiert und ist beschreibbar.: Ja (“$ABSPATH/wp-content/uploads/matomo/config/config.ini.php” )
* JS Tracker existiert und ist beschreibbar.: Ja (“$ABSPATH/wp-content/uploads/matomo/matomo.js” )
* Plugin-Verzeichnisse: Yes ([{“pluginsPathAbsolute”:”$ABSPATH\/wp-content\/plugins\/matomo\/plugins”,”webrootDirRelativeToMatomo”:”..\/”}])
* Tmp-Verzeichnis schreibbar: Yes ($ABSPATH/wp-content/cache/matomo)
* Matomo-Version: 4.0.5
* Matomo Blog idSite: 1
* Installierte Matomo-Version: 4.0.4 (Install date: 2020-12-11 19:08:32)
* Upgrades outstanding: No
* Upgrade in progress: No

## Endpoints

* Matomo JavaScript Tracker URL: ($site_url/wp-content/uploads/matomo/matomo.js)
* Matomo JavaScript Tracker – WP Rest API: ($site_url/wp-json/matomo/v1/hit/)
* Matomo HTTP Tracking API: ($site_url/wp-content/plugins/matomo/app/matomo.php)
* Matomo HTTP Tracking API – WP Rest API: ($site_url/wp-json/matomo/v1/hit/)

## Crons

* Server-Zeit: 2020-12-11 18:10:52
* Blog-Zeit: 2020-12-11 19:10:52 (Die nachfolgenden Daten werden in der Blog-Zeitzone angezeigt)
* Sync users & sites: Next run: 2020-12-12 19:08:31 (23 Stunden 57 Minuten) ( Last started: 2020-12-11 19:10:26 (-26 Sek.). Last ended: 2020-12-11 19:10:26 (-26 Sek.). Interval: daily)
* Archive: Next run: 2020-12-11 20:08:31 (57 Minuten 39s) ( Last started: 2020-12-11 19:10:26 (-26 Sek.). Last ended: 2020-12-11 19:10:41 (-11 Sek.). Interval: hourly)
* Update GeoIP DB: Next run: 2021-01-10 19:08:31 (29 Tage 23 Stunden) ( Last started: 2020-12-11 19:10:41 (-11 Sek.). Last ended: 2020-12-11 19:10:44 (-8 Sek.). Interval: matomo_monthly)

## Vorgeschriebene Prüfungen

* PHP-Version >= : ok
* PDO Erweiterung: ok
* PDO\MYSQL Erweiterung: ok
* MYSQLI Erweiterung: ok
* Weitere erforderliche Anforderungen: ok
* Erforderliche Funktionen: ok
* Ben?tigte PHP Konfiguration (php.ini): ok
* Verzeichnisse mit Schreibzugriff: ok
* Verzeichnisse mit Schreibzugriff auf Tag Manager: ok

## Optionale Prüfungen

* Tracker-Status: ok
* Speicherlimit: ok
* Zeitzone: ok
* ?ffnen einer URL: ok
* PageSpeed deaktiviert: ok
* GD > 2.x + Freetype (graphics): ok
* Andere Erweiterungen: ok
* Warning Andere Funktionen: warning (shell_exec Sie müssen diese eingebaute Funktion aktivieren set_time_limit mail parse_ini_file glob gzopen md5_file )
* Dateisystem: ok
* Letzter erfolgreicher Abschluss der Archivierung: ok
* Datenbankf?higkeiten: ok
* Warning Maximale Packetgr??e: warning
* Standorterkennung: ok
* Update über HTTPS: ok
* Schreibbarer JavaScript-Tracker (“/matomo.js”): ok
* Supports Async Archiving: No
* Location provider ID: geoip2php
* Location provider available: Yes
* Location provider working: Yes

## Matomo Settings

* Track mode: default
* Track codeposition: footer
* Track api endpoint: default
* Track js endpoint: default
* Version history: 4.0.4
* Core version: 4.0.5
* Last tracking settings update: 1607710226
* Last settings update: 1607710226

## Logs

# WordPress

* Home URL: $site_url
* Site URL: $site_url
* WordPress Version: 5.6
* MATOMO_SUPPORT_ASYNC_ARCHIVING: –
* MATOMO_TRIGGER_BROWSER_ARCHIVING: –
* MATOMO_ENABLE_TAG_MANAGER: –
* MATOMO_SUPPRESS_DB_ERRORS: –
* MATOMO_ENABLE_AUTO_UPGRADE: –
* MATOMO_DEBUG: –
* MATOMO_SAFE_MODE: –
* MATOMO_GLOBAL_UPLOAD_DIR: –
* MATOMO_LOGIN_REDIRECT: –
* Permalink Structure: /%category%/%postname%/
* Compatible content directory: Yes

# WordPress Plugins

## Plugins

* LiteSpeed Cache: 3.5.2
* Matomo Analytics – Ethical Stats. Powerful Insights.: 4.0.4

# Server

* Server Info: LiteSpeed
* PHP OS: Linux
* PHP Version: 7.4.6
* PHP SAPI: litespeed
* PHP Binary Name: lsphp
* Timezone: UTC
* WP timezone: Europe/Berlin
* Locale: de_DE
* User Locale: de_DE
* Memory Limit: 256M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
* WP Memory Limit: 40M
* WP Max Memory Limit: 256M
* Max Execution Time: 60
* Max Post Size: X
* Max Upload Size: X
* Max Input Vars: 10000
* Disabled PHP functions: Yes (getmypid, passthru, leak, listen, diskfreespace, link, ignore_user_abord, shell_exec, dl, exec, system, highlight_file, source, show_source, fpaththru, virtual, posix_ctermid, posix_getcwd, posix_getegid, posix_geteuid, posix_getgid, posix_getgrgid, posix_getgrnam, posix_getgroups, posix_getlogin, posix_getpgid, posix_getpgrp, posix_getpid, posix, _getppid, posix_getpwnam, posix_getpwuid, posix_getrlimit, posix_getsid, posix_getuid, posix_isatty, posix_kill, posix_mkfifo, posix_setegid, posix_seteuid, posix_setgid, posix_setpgid, posix_setsid, posix_setuid, posix_times, posix_ttyname, posix_uname, proc_open, proc_close, proc_get_status, proc_nice, proc_terminate, phpinfo, eval)
* zlib.output_compression is off: Yes
* Curl Version: 7.62.0, OpenSSL/1.0.2k

Hi there,

I have the same issue. Can login without entering GA code and even with a random code, e.g. 123456. The difference is, I do not have any of the above mentioned plugins installed. In fact, I try to keep installed plugins at a minimum. Although, I have WP-Client installed. May that interfere with this plugin?

Thanks!

Cheers