Hi,
I just tried it in 5.7 and it’s working for me.
Do other changes save properly? For example, the title? And you said no console errors when you press save?
What’s the URL you are adding to the field? Does another URL work like google.com?
– Do other changes save properly?
No, the same happens with GENERAL tab or SEO tab. I complete the field, save the changes and when I reload the meta slider admin page, the content dissapear. Only Works the image for me.
– You said no console errors when you press save?
Yes no errors. I see this code when i save in the console.
MetaSlider: MetaSlider dashboard loaded
app.min.js?ver=3.20.3:2 MetaSlider: Guardando…
app.min.js?ver=3.20.3:2 MetaSlider: Settings saved
– What’s the URL you are adding to the field? Does another URL work like google.com?
I tried a lot of urls. Included http://www.google.com
Hi,
Can you check the slider saving functionality? It’s done using AJAX.
This article will guide you on how to monitor the AJAX calls: https://www.codexworld.com/how-to/monitor-ajax-requests-google-chrome/
Can you please enable WordPress debugging: https://wordpress.org/support/article/debugging-in-wordpress/
After enabling the debug mode, please replicate the issue and share with me the latest error logs in your WordPress error log file.
You may also ask your hosting provider to provide you the PHP error log and share it with me.
Hi!
The debug mode is set to true and there is no error messages. I am working in a kinsta hosting.
Ajax calls when I save:
================================================
Name: save
Response: {“success”:true,”data”:38000000017069}
Name save
Response: {“success”:true,”data”:”OK”}
===================================================
HEADERS
Request URL: https://staging-emama.kinsta.cloud/wp-json/metaslider/v1/settings/slideshow/save
Request Method: POST
Status Code: 200
Remote Address: [2606:4700:7::a29f:862a]:443
Referrer Policy: strict-origin-when-cross-origin
access-control-allow-headers: Authorization, X-WP-Nonce, Content-Disposition, Content-MD5, Content-Type
access-control-expose-headers: X-WP-Total, X-WP-TotalPages, Link
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400
cache-control: no-cache, must-revalidate, max-age=0
cf-cache-status: DYNAMIC
cf-ray: 631ac2c29deaf816-EZE
cf-request-id: 08e4980da10000f8160facd000000001
content-encoding: gzip
content-type: application/json; charset=UTF-8
date: Thu, 18 Mar 2021 01:41:48 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expires: Wed, 11 Jan 1984 05:00:00 GMT
ki-edge: v=3
link: <https://staging-emama.kinsta.cloud/wp-json/>; rel="https://api.w.org/"
server: cloudflare
vary: Accept-Encoding
x-content-type-options: nosniff
x-edge-location-klb: 1
x-robots-tag: noindex
x-robots-tag: noindex, nofollow, nosnippet, noarchive
x-wp-doingitwrong: wp_send_json (desde 5.5.0; Devuelve un objeto WP_REST_Response o WP_Error desde tu llamada de retorno al usar la API REST.)
x-wp-nonce: 6a794d2056
:authority: staging-emama.kinsta.cloud
:method: POST
:path: /wp-json/metaslider/v1/settings/slideshow/save
:scheme: https
accept: application/json, text/plain, */*
accept-encoding: gzip, deflate, br
accept-language: es-US,es;q=0.9,es-419;q=0.8,en;q=0.7,pt;q=0.6
content-length: 2685
content-type: multipart/form-data; boundary=----WebKitFormBoundaryiSfq7gy69Arh75Fc
cookie: wp_automatewoo_visitor_ce494d07492c33b36055f282e62f8420=kvnti7w9zjogvi4oz39s; _ga=GA1.2.1713484559.1612373451; _fbp=fb.1.1612373451767.1025846748; wp-settings-1=libraryContent%3Dbrowse%26editor%3Dhtml%26mfold%3Do%26hidetb%3D1%26posts_list_mode%3Dlist; wp-settings-time-1=1615522064; _gid=GA1.2.1620686268.1616030502; wordpress_test_cookie=WP%20Cookie%20check; wordpress_logged_in_ce494d07492c33b36055f282e62f8420=agenciabrandi%7C1616203342%7CGv8NIk4Eb3wfDFg2kKZVGrxMkxSwV8YDUBvgbPm2hxH%7C889fe2bf4bf0af2b0dff5a50267f3188feef7cf18e75e56867b8a2638bbebf43; tk_ai=woo%3ABSk3Zmb5DyioGRAkvsRIb%2FoJ; mp_a36067b00a263cce0299cfd960e26ecf_mixpanel=%7B%22distinct_id%22%3A%20%22177e118038d226-0b90ed59ce7fc4-53e356a-1fa400-177e118038e52e%22%2C%22%24device_id%22%3A%20%22177e118038d226-0b90ed59ce7fc4-53e356a-1fa400-177e118038e52e%22%2C%22%24initial_referrer%22%3A%20%22https%3A%2F%2Fstaging-emama.kinsta.cloud%2Fwp-admin%2Fplugins.php%22%2C%22%24initial_referring_domain%22%3A%20%22staging-emama.kinsta.cloud%22%7D
origin: https://staging-emama.kinsta.cloud
referer: https://staging-emama.kinsta.cloud/wp-admin/admin.php?page=metaslider&id=38000000017069
sec-ch-ua: "Google Chrome";v="89", "Chromium";v="89", ";Not A Brand";v="99"
sec-ch-ua-mobile: ?0
sec-fetch-dest: empty
sec-fetch-mode: cors
sec-fetch-site: same-origin
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.82 Safari/537.36
x-requested-with: XMLHttpRequest
x-wp-nonce: 6a794d2056
slideshow_id: 38000000017069
action: ms_update_all_slideshow_settings
settings[type]: flex
settings[width]: 1600
settings[height]: 450
settings[effect]: slide
settings[links]: on
settings[navigation]: true
settings[fullWidth]: on
settings[center]: on
settings[autoPlay]: on
settings[smartCrop]: disabled
settings[carouselMargin]: 5
settings[hoverPause]: on
settings[delay]: 1000
settings[animationSpeed]: 600
settings[direction]: horizontal
settings[easing]: linear
settings[prevText]: Anterior
settings[nextText]: Siguiente
settings[cssClass]: slide-web
settings[printCss]: on
settings[printJs]: on
settings[noConflict]: on
Hi,
This seems to be very tricky. this issue should be something specific to your installation. You already did all the troubleshooting steps without succeeding to find the issue cause.
The following would help you:
Did you try to save the URLs in a new slideshow?
Does the same issue happen in another host or your local machine?
Can you try MetaSlider on a fresh WordPress installation?
The previous questions seem to be generic but the troubleshooting steps you already did shows that nothing wrong with MetaSlider. So, we need to think in a different way.
Hello! I tested the slide on a clean local install of wordpress and the links works!
Honestly, I do not know what to think, since the previous tests were done with Storefront, Worpress 5.7 and without any activated plugin. Could something in my database be generating this error?
Can you check this with your hosting provider? Maybe they have a clue.
