Toru Miki

Thank you for the update and the comment Scott!

@alexrollin Thanks for fixing the issue. When is the nest release is going to be released?

追記。

マルチサイトで、サイト毎に個別に有効化?無効化している場合、下記事象も発生しました。

例
– メインサイト
– blog_id = 2　（wovn有効化、設定保存済み=wovn_optionsがあり、値も空ではないが wovn_translate_canonical_tag は無い状態）
– blog_id = 3
– blog_id = 4　（wovn有効化、設定未保存=wovn_optionsが無い状態）

この状態で1.7から1.8へアップデートすると……
blog_id = 2 => 上記に記した通り
blog_id = 4 => エラーのため管理画面へアクセスできなくなり、メインサイトの管理画面へリダイレクトされる

WP-CLIで blog_id=4 で有効化されているwovn-ioを無効化してアクセスできるようになりました。

@kbat82 Thanks!

I checked var_dump() first, which returned me https://admin.example.com/wp-json/. Tried that first, but with no luck, so I tried the full url with /metaslider/v1, and this worked.

But I am now getting a new error.

MetaSlider: Saving…
VM608:1 POST https://admin.example.com/wp-json/metaslider/v1/themes/all?action=ms_get_all_free_themes/slideshow/save 404
(anonymous) @ VM608:1
(anonymous) @ app-3-14-0.js:1
t.exports @ app-3-14-0.js:1
t.exports @ app-3-14-0.js:1
Promise.then (async)
s.request @ app-3-14-0.js:1
s.<computed> @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
save @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
c @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
t.<computed> @ app-3-14-0.js:1
ve @ app-3-14-0.js:1
a @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
xe.methods.save @ app-3-14-0.js:1
keydown @ VM641:3
Ut @ app-3-14-0.js:1
n @ app-3-14-0.js:1
Jr.i._wrapper @ app-3-14-0.js:1
app-3-14-0.js:1

MetaSlider: undefined

Also, under Network > XHR > Preview, nothing there — just 404.

(unlike https://www.ads-software.com/support/topic/problems-to-save-pictures/ )

Thanks @kbat82,

I tried add_filter(‘rest_url’), and now the “blocked by CORS policy” error is gone. But I now get 404 and continue to get “Cannot read property data…”.

`
VM989:1 GET https://admin.example.com/themes/all?action=ms_get_all_free_themes 404
(anonymous) @ VM989:1
(anonymous) @ app-3-14-0.js:1
t.exports @ app-3-14-0.js:1
t.exports @ app-3-14-0.js:1
Promise.then (async)
s.request @ app-3-14-0.js:1
s.<computed> @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
fetchThemes @ app-3-14-0.js:1
mounted @ app-3-14-0.js:1
Ut @ app-3-14-0.js:1
en @ app-3-14-0.js:1
insert @ app-3-14-0.js:1
S @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
t._update @ app-3-14-0.js:1
r @ app-3-14-0.js:1
mn.get @ app-3-14-0.js:1
mn @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
Cn.$mount @ app-3-14-0.js:1
Cn.$mount @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
n @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
n @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1
(anonymous) @ app-3-14-0.js:1

app-3-14-0.js:1 Uncaught (in promise) TypeError: Cannot read property ‘message’ of undefined
at app-3-14-0.js:1
`

Hi Uriahs,

Thank you for a quick response! I checked on my local environment and production environment, and seems to get no error. Yes, look fixed.

I now realized I was using a slightly old version of the plugin, because it was an old UI. Though I kept all plugins up-to-date, and I never saw any notifications for this plugin… anyways it is solved.

Regards,
Toru

• This reply was modified 6 years, 10 months ago by Toru Miki.

Hi Jasper,

Thanks for the reply!

I should also have posted earlier, but I solved it temporally by preg_replace just the post thumnail.

$sizes_for_post_thumbnail = 'sizes="(max-width: 600px) calc(100vw - 20px), (max-width: 680px) calc(((100vw - 20px) * 1.02) * 0.48), (max-width: 920px) calc((((100vw - 20px) * 0.742) * 1.02) * 0.48), calc((((100vw - 20px) * 0.742) * 1.02) * 0.3133333), 270px"';
$tujnews_the_post_thumbnail = get_the_post_thumbnail( get_the_ID(), 'post-thumbnail-large' );
$tujnews_the_post_thumbnail = preg_replace( '/sizes="(.*)"/', $sizes_for_post_thumbnail, $tujnews_the_post_thumbnail );
echo $tujnews_the_post_thumbnail;

I thought this was not a good solution performance wise, but felt feasible solution for now, since I could not figure out how to specify for a particular thumbnail.

Thank you also for the update on version 3.0. I have actually been following all the development discussion on slack, and I am aware of it, including that the name of filter might change again.

(hence I implemented above as a temporally solution)
(I was not sure whether to post this here or on slack, but since it is “how-to” question, I posted here on the forum)

I will update the filter to use wp_get_attachment_image_sizes().

As for specifying different sizes value for different image/image sizes/thumbnail, I think Joe’s answer below is also useful to me, so I will look into it.
https://www.ads-software.com/support/topic/firefox-not-loading-in-larger-images-on-resize#post-7637254

OK, I will have a go on that. Thanks.

I have been running into same issue, trying to use posts2posts with Tri.be’s event calendar/PRO. It is Event Calendar issue, and you can find the solution and explanation here. (and in github linked to it)

https://tri.be/support/forums/topic/possible-conflict-with-the-plugin-post-to-post/

The filter worked on mine so far, on “basic usage”. I hope this helps.

Ah! of course! Why didn’t think of that…not a bug then, good ??
Thanks Dominik.

I think this is a great idea. There are definitely some loose ends that needs to be tied.

one suggestions for Web site content of www.ads-software.com:
A page which contains links to .org related sites. ie. wordpress.tv, wordcamp, wp jobs … as well as dev links like dev blog, etc. would be good. I just noticed some of these links at the footer, but no many people are gonna to notice that ??
I am not sure in other countries, but at least in Japan, although many know www.ads-software.com, most doesn’t know these related sites exists. I think because simply the links aren’t clear on this “official” .org site. A page with not just list of links, but with screenshot and short description of what these sites are will be, I think, particularly useful for newbies.

Woo Hoo! A reply!

no. no one with how to fix. Inow don’t use it anymore. Though not to do with the plugin bug issue. I think, if my memroy serves correct, it got slightly better with the later version. What its like now, I have no idea…

*UPDATE*

It someties duplicates two posts now as well.