Giuseppe
Forum Replies Created
-
Forum: Plugins
In reply to: [No unsafe-inline] Problem with upgrade to 1.3.0Please, send an URL to the page.
Try to regenerate the trained estimators (run cluster scripts) and let me know if this solve the problem
Forum: Plugins
In reply to: [No unsafe-inline] How to add other headers to the CSPYou can extend the CSP served by the plugin using a custom function and hooking in to nunil_output_csp_headers_header_csp with apply_filter()
Forum: Plugins
In reply to: [No unsafe-inline] SHA256 not loadingsorry for answering so late. Using hashes cannot work if your server offers the prechaced page. Rehasing is usefull only if some unversioned scripts are changed, but use the same name
Forum: Plugins
In reply to: [No unsafe-inline] Google youTube, reCaptcha integrity failureHi @w3bdevguru,
it could be possible that some api, doesn’t offer the same js to all agents. So for those you cannot use SRI and hashes because the js can change on different requests.
I added a hook to solve this situation: no_unsafe_inline_not_sri_sources
This is the merged PR: https://github.com/MocioF/No-unsafe-inline/pull/20
I think you should use a custom function tho hook into the $not_sri_sources array and add those domains
Please, can you test the development version (v. 1.2.6-dev)?
Forum: Plugins
In reply to: [No unsafe-inline] Problem with recaptcha during capture phasePlease, can you test the development version (v. 1.2.6-dev)?
Forum: Plugins
In reply to: [No unsafe-inline] Activating the plugin does nothingHi @jmanuelluis @jakegrabowski , I think the issue is related to the libxml version that php is using.
I have opened a bug for this on the project of the library used to parse HTML5 https://github.com/ivopetkov/html5-dom-document-php/issues/63
In the meanwhile, I have introduced a workaround to not use html5-dom-document if PHP version is 8.4 or if libxml version is > 2.13.9.
The patched version of No unsafe-inline is now in the development version available in SVN: https://downloads.wp.xz.cn/plugin/no-unsafe-inline.zip and will be released with next version 1.2.4.
I would be glad if you could test the development version in your environment and write here if the bug is fixed.
Forum: Plugins
In reply to: [Campi Moduli Italiani] Problema salvataggio colonne regione/provincia/comunePremetto che non ho fatto un test, ma sembra sia una modifica effettuata a CFDB7 recentemente, che non consente il salvataggio degli input hidden.
Prova a seguire questo:
Forum: Plugins
In reply to: [Campi Moduli Italiani] Problema salvataggio colonne regione/provincia/comune- Per piacere posta il link alla pagina in cui è presente il form
- CF7 non salva dati sul db; per farlo stai utilizzando un altro plugin. Puoi verificare eventuali impostazioni di questo plugin e dire quale è?
- per verificare che i dati vengano tutti trasmessi, puoi provare il plugin flamingo e controllare se hai tutti i campi nell’output
Forum: Plugins
In reply to: [Campi Moduli Italiani] Errore aggiornamento campiBuongiorno @claudiamazzinghi, realisticamente il problema di download era dovuto alla scadenza del certificato pem del server istat. Il problema dovrebbe essere risolto, aggiornando alla versione 2.3.1.
L’altro problema immagino derivi da qualche modifica effettuata su CFDB7 ma al momento non so darti una soluzione. Potresti fare qualche esempio di dati “differenti”?
- This reply was modified 7 months, 2 weeks ago by Giuseppe.
Forum: Plugins
In reply to: [Campi Moduli Italiani] Un paio di richieste davvero desiderateGrazie dei suggerimenti Riccardo.
La prima richiesta, in realtà, non è banale perché richiederebbe la modifica delle query inviate al database. Il secondo suggerimento potrebbe essere implementato.
Se possibile, ti chiedo di inserire le richieste direttamente nel repository github, in modo da poterle tracciare in fase di sviluppo: https://github.com/MocioF/campi-moduli-italiani/issues
Saluti
Forum: Plugins
In reply to: [No unsafe-inline] Activating the plugin does nothingInto includes/class-no-unsafe-inline-activator.php you can see the tables that should be created upon activation.
In your site, the mu-plugin is in place and the plugin seems active with capture enabled because the rest route is active: https://preempresaysalud.amat.es/wp-json/no-unsafe-inline/v1/
Can you enable WP_DEBUG and/or WP_DEBUG_LOG, then deactivate and reactivate the plugin and post here any message showed in console or registered in log?
Forum: Plugins
In reply to: [No unsafe-inline] Activating the plugin does nothingPlease share the site URL
Forum: Plugins
In reply to: [No unsafe-inline] Fatal error after upgrading to v1.2.3Nice shot @cbre: I didn’t think about this.
When updating to a new RubixML version, we have to regenerate (or better, retrain) the classifier because now rubixml checks for compatibility in this way:
https://github.com/RubixML/ML/commit/2768760778789b61b1469927d4e4d19c21053b81
No unsafe-inline 1.2.2 shipped with rubix 2.5.1, while version 1.2.3 ships with rubixml 2.5.2.
I think I will add a step on plugin update to train the classifier if rubixml is updated.
Forum: Plugins
In reply to: [No unsafe-inline] Fatal error after upgrading to v1.2.3no, the problem is not in the package. I checked it twice after your request.
And I was wrong when I said it could be related to the change in namespace I did in the last version.
Today I couldn’t reproduce the issue. Now I think you don’t have a required PHP extensions. I will check if the last rubixml package requires something more than previous version.
In the meanwhile, can you post a list of PHP extensions running on your server?