aschi
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Sydney] No customizing menu and warningHi @kharisblank and @joannapol,
Yes, the problem is solved with Sydney-update to version 2.49!
Thank you very much. Best Regards Aschi
Forum: Themes and Templates
In reply to: [Sydney] No customizing menu and warningHy,
it is definitely a problem of sydney, version 2.48. I tested on my local server all versions of sydney taken from my backups. Result: untill version 2.47 there are no problems (no warnings showed when customizing).
But with the last update (december 2024) to version 2.48 all warnings are here again! So we wait for version 2.49 and hope the problems will be fixed in the next version.
Astonishing: on my online-site uses version 2.48 without issues! only on a local host there are warnings witgh version 2.48.
As I cannot do anything more, I leave the problem as “unsolved”.
Regards Aschi
Forum: Themes and Templates
In reply to: [Sydney] No customizing menu and warningTheme-version problem?
I took an older version of the theme sydney (free) from a backup: v.2.41 – and the warnings are all gone!!!
With sydney V. 2.41 everything works – except the word press site health check moaning “theme not updated”.
So I wait for the next theme update and hope that will fix it.
Regards, Aschi
Forum: Themes and Templates
In reply to: [Sydney] No customizing menu and warningHy,
it is not the php-version. I just tested on my local server. Instead of php v. 8.2.22 I used php the older version 8.1.31. But the warnings are still there. And because the server for my online-page https://aschihaas.ch is using the same php-version (8.1.31) and shows no warnings, the problem has to be somwhere else.
If I have a look at the file quoted in the warnings, class-sydney-style-book.php, there is a comment about “fonts for all hedings”:
//Headings
//we currently only support one font for all headings
$headings = json_decode( get_theme_mod( ‘sydney_headings_font’ ), true );Maybe this causes the warnings? But I still have no idea how to fix it!
Regards Aschi
Forum: Plugins
In reply to: [Gallery Custom Links] Settings not acessibleHi,
I tried your Plugin again today: and now it works without any problem!!!
I do not know whether the problem has gone because of the update to WordPress 6.1.1 or if my Hosting Company changed something – anyhow, it is solved!I put the status to “resolved”.
Thank you very much,
AschiForum: Plugins
In reply to: [Gallery Custom Links] Settings not acessibleHi,
uninstalling and reinstalling the plugin today, result:
– no error in wordpress-test about website state, it says “excellent work”
– but the plugin-setting page is empty, I can try via “plugin/gallery custom link/settings”, via meow-apps, dashboard or custom links – there is always an empty page
– if I do right-click and choose “investigate” in wordpress dashboard, then console and error, I get the message I copied at the end of my text
– I made a test-gallery with a cxustom link, but it did not work
Thank you for further investigations!
Regards AschiHere the Text from error console:
x mgcl_gallery_custom_links {api_url: 'https://www.aschihaas.ch/wp-json/gallery-custom-links/v1', rest_url: 'https://www.aschihaas.ch/wp-json/', plugin_url: 'https://www.aschihaas.ch/wp-content/plugins/gallery-custom-links/', prefix: 'mgcl', domain: 'gallery-custom-links', …} react-dom.min.js?ver=17.0.1:9 Uncaught Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20wi…0keys%20%7Btype%2C%20key%2C%20ref%2C%20_owner%2C%20_context%2C%20_store%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at qn (react-dom.min.js?ver=17.0.1:9:35871) at react-dom.min.js?ver=17.0.1:9:40705 at Dt (react-dom.min.js?ver=17.0.1:9:48794) at os (react-dom.min.js?ver=17.0.1:9:112745) at Ur (react-dom.min.js?ver=17.0.1:9:77643) at Ir (react-dom.min.js?ver=17.0.1:9:77571) at Dr (react-dom.min.js?ver=17.0.1:9:77434) at Pr (react-dom.min.js?ver=17.0.1:9:74429) at Er (react-dom.min.js?ver=17.0.1:9:72010) at ul (react-dom.min.js?ver=17.0.1:9:87836) admin.php:1 Unchecked runtime.lastError: The message port closed before a response was received.
Forum: Plugins
In reply to: [Gallery Custom Links] Settings not acessibleHi,
Thew plugin does not work, it says something about runtime error, and my provider did not change anything.
Therefore this plugin is unusable – at least for me!Regards,
AschiForum: Plugins
In reply to: [Gallery Custom Links] Settings not acessibleHi,
The problem is not resolved, I wonder who set it to “resolved”!
And of course, if it is set to “resolved”, nobody helps.But I does not work, does not add the needed Links.
But I still cannot understand, why the plugin worked for a long time and now, after the last update, it would not.
If I get no help in the next days, I have to delete it and look for other solutions.
Kind regards,
AschiForum: Plugins
In reply to: [Gallery Custom Links] Settings not acessibleHere what I fould on my dashboard, perhaps this may help:
mgcl_gallery_custom_links {api_url: 'https://www.aschihaas.ch/wp-json/gallery-custom-links/v1', rest_url: 'https://www.aschihaas.ch/wp-json/', plugin_url: 'https://www.aschihaas.ch/wp-content/plugins/gallery-custom-links/', prefix: 'mgcl', domain: 'gallery-custom-links', …} www.aschihaas.ch/:1 Unchecked runtime.lastError: The message port closed before a response was received. {api_url: 'https://www.aschihaas.ch/wp-json/gallery-custom-links/v1', rest_url: 'https://www.aschihaas.ch/wp-json/', plugin_url: 'https://www.aschihaas.ch/wp-content/plugins/gallery-custom-links/', prefix: 'mgcl', domain: 'gallery-custom-links', …} load-scripts.php?c=1…p-hooks&ver=6.0.3:5 JQMIGRATE: Migrate is installed, version 3.3.2 main.min.js?ver=6.0.3:1 Download the React DevTools for a better development experience: https://fb.me/react-devtools
Forum: Plugins
In reply to: [Gallery Custom Links] Settings not acessibleI am coming back to my question: why does the plugin not work?
I have a local backup and development environement with xampp and apache on Windows 10. There the plugin works without a problem.On my online-site https://www.aschihaas.ch the last update went wrong, it hang up. Up to then, it worked. Now I tried several uninstall and reinstall, but
– the dasboard shows an empty page, so I have no possibility to look for an php error
– the plugin does not work, in the Medias there are no fields with “Link URL and Link Target”I tried to copy the whole plugin file from the test system to the online – but the problem is still there, online it does not work.
There must be a history somewhere or another entry (perhaps in the database?) that prevents the plugin to work. Strange, bevore that misleaded update it worked!
Do you see any reason for this behavior? Or do I have to look for an other solution?
Thank you for your answer.
Regards AschiForum: Plugins
In reply to: [Gallery Custom Links] Settings not acessibleHi,thank you for your quick answer.
Console Developer Tool? I Just have the WordPress Dashboard, and when I Meow Apps Dashboard, it says:
“Thanks for using Meow Apps! This is the Meow Admin 3.7
Loaded from /storage/content/74/2115174/aschihaas.ch/public_html/wp-content/plugins/gallery-custom-links/common/admin.php Version 6.0.3”
The Page “custom links” ist completely empty, it just sayx “Danke für Ihr Vertrauen in WordPress”!
Redards, Aschi@mateusz Thank you for your answer. I understand that you cannot see why this happend on my local system. I am glad to hear that your plugin is quite popular and works on many sites.
But as the plugin does not work on my test-system (for any reason) I would not dare to implement it on myx live-site. So I will uninstall it.Thank you and kind regards,
AschiHi@mateusz,
I just enabled the debug and got some entries. I think the PHP-errors are important. I copied it and insert it further down. Theoretically the debug-file should be downloadable, but it would not work on my local installation.
I also tried to deactivate my picture-plugins, i.e. foogallery and foobox-imige-lightbox, but the error is still there. Hope that the debug extract will help, here08:46:00 GMT+0200 (Mitteleurop?ische Sommerzeit) The magic method AllbitsnbytesWPLogViewerCharacteristicIsSingleton::__wakeup() must have public visibility A:xampphtdocsaschiwp-contentpluginswp-log-viewerlibsCharacteristicIsSingleton.php on line 58 Type: PHP Warning Line: 58 More details Today 08:46:00 GMT+0200 (Mitteleurop?ische Sommerzeit) Private methods cannot be final as they are never overridden by other classes A:xampphtdocsaschiwp-contentpluginswp-log-viewerlibsCharacteristicIsSingleton.php on line 58 Type: PHP Warning Line: 58 More details Today 08:46:00 GMT+0200 (Mitteleurop?ische Sommerzeit) Private methods cannot be final as they are never overridden by other classes A:xampphtdocsaschiwp-contentpluginswp-log-viewerlibsCharacteristicIsSingleton.php on line 50 Type: PHP Warning Line: 50 More details
If you see anything, we will work on. But I do not wante to waste your time: something on my localhost must be special.
Thank you and kind regards Aschi@mateusz,
If I deactivate your plugin the error is away! Maybe it would not work with my other plugins. But I need them.
Perhaps I should wait until WordPress integrates webP…
Best regards AschiHi Mateusz,
Tank you for your answer. The message comes from WordPress, when I ask for the health of my installation (It is set in Germann: Dashboard>Werkzeuge>Webseiten-Zustand).The message of “Loopback error” I had yesterday has gone, but the Rest-API is still here:
“Die REST-API-Anfrage ist aufgrund eines Fehlers fehlgeschlagen.
Fehler: cURL error 28: Operation timed out after 10007 milliseconds with 0 bytes received (http_request_failed)”Best,
Aschi