temereva
Forum Replies Created
-
Thank you for the prompt response, Koen. I tried connecting multiple times yesterday and once today, with the sale result. I’m wondering if it might have something to do with the amount of connections? Our organization uses this plugin for multiple properties in our GMB, and at the moment of connection, the first response I received was this: “posttogmb.com already has some access”, and with the next step it returns the error I mentioned earlier: Could not verify Google access token: “keys” member must exist in the JWK Set.
Do you have any other suggestion?Thank you,
Eva
Thank you, <span class=”bbp-author-name”>andrewshu</span> . I found the issue.
The conflict was with the plugin Real Simple SSL, where we enabled the recommended option “Restrict listing the users”. It apparently restricted ajax to invoke get_posts function by specified author.
However, it would be nice to have error handling there for the cases like this, when when the query does not return the expected result.
In my case the query returns a phrase “Not allowed” with the author id instead of the query results and it is being posted to the page without any validation. This makes user experience very confusing, and it also exposes the author ID unnecessary.
Thanks again for your plugin. It’s really great.Forum: Plugins
In reply to: [Comet Cache] Referrer-Policy header is being omittedThank you, @raamdev !
That’s great to know! Thank you! I can confirm that it’s fixed.
Found the issue and a few ways to fix it.
The main problem is that getDocs() function is supposed to return a string, but there are cases where it returns “false” or an empty array, and in Vue.php file there is no check for the data type, hence – the json_decode() function that expects for the string only throws a notice into my php log on every load of the page/post edit screen.
Fixes:
In short, @shivamtyagi , it would be great if you just added a simple datatype check to Vue.php.(is_string(aioseo()->help->getDocs()) === true) ? json_decode( aioseo()->help->getDocs()) : ”,
If more detailed, getDocs() function can also be revised to ensure it returns same type of response.
Also, in my case the core of the problem was that my WordPress is configured to limit the external http requests to a few that are absolutely necessary (for various reasons). So when getDocs() can’t get the docs from WP cache, it tries to fetch it from the plugin’s cdn, and receives wp_error object. Ideally, there should be a message thrown to the admin panel offering to add the specified domain name to the accessible hosts: define(‘WP_ACCESSIBLE_HOSTS’, ‘*.aioseo.com’); in wp-config.php – this would fix the logging issue too.
Hello,
I’m receiving the same warning after updating to the version 4.2.2.
PHP Warning: json_decode() expects parameter 1 to be string, array given in …/wp-content/plugins/all-in-one-seo-pack/app/Common/Traits/Helpers/Vue.php on line 162it’s the same line:
‘helpPanel’ => json_decode( aioseo()->help->getDocs() ),It’s logged every time I load or save any “edit” screen in WP admin, for any post type, including media.
Could you please take a look at this?
EvaForum: Plugins
In reply to: [Safe SVG] Fatal ErrorHello,
I have the same issue when installing the plugin on the WP 5.6. Any updates?- This reply was modified 3 years, 11 months ago by temereva.
Perfect! This helped. Thanks a lot!
Some posts do have shares on the second website.
https://prntscr.com/nd303zThank you for the quick response,
Since the URL was not changed, could the changing of the post publishing date have the same result?
Another question: in the previous plugin version (I didn’t yet update it on another website) the shortcode displays the counter info, even if it’s 0 (example:https://holmesapprovedhomes.com/builder-blogs/our-commitment-to-energy-efficiency/). In the new version it does not. Is this how you intended it to be? (Just trying to make sure I don’t have any script that prevents the data to be printed on the page correctly).
Thank you!
I solved the issue this way: in the folder plugins/redux-framework/sample I renamed the sample-config.php (to disable it), when it’s done, after refreshing the plugins page in the WP dashboard it loaded normally and showed the link “disable the demo mode”. This worked.
Replying to Dovy’s question:
I’ve just recreated the issue with all the other plugins disabled. I’ve got the same message: “Sorry, you are not allowed to access this page”Eva
Forum: Plugins
In reply to: [WP Store Locator] Wp Store Locator: back end store search does not workHaven’t tried yet. But here is what helped me: I’ve commented out the search filter in the theme’s functions.php, the one that excluded pages from the search results, when you search only in posts. I guess, there is some “misunderstanding” between the theme and the Store Locator about the post type the plugin use to display the stores.
Below is the code:
/*function searchExcludePages($query) {
if ($query->is_search) {
$query->set(‘post_type’, ‘post’);
}
return $query;
}
add_filter(‘pre_get_posts’,’searchExcludePages’);*/
/*