maven1129

Hi Michael,

When I add this CSS:

.algolia-autocomplete {

? ? position: fixed !important;

? ? overflow-y: auto !important;

? ? max-height: 50vh !important;

}

It prevents the issue. But, with or without these changes, the results make the body scrollable when before they were shown, the body was not scrollable (this search box is inside a modal, for example, that prevents background scrolling). It also takes two taps on the backdrop to remove the element and trult interact with the page behind it. I noticed that there are two spans on the page being added with the same class as i target above in the css, so not sure if that’s part of it or not.

I would like to be able to target my own div for displaying the autocomplete results, which would likely enable me to control all this is a much batter way. Should I email for support on getting that upgrade to 1.0?

I see what you mean. Is_admin is a tag id have to add to detect that the php errors occurred on the backend?

This works on Pages, but on custom post types, there is no “Template” drop down in quick edit – even for those custom post types with “Page Attributes” enabled. Any ideas?

That is not a good start. That is as bare bones of an API document as I have ever seen. You guys really need to invest into opening up other paramters of the link creation API, and properly document it. STOP DELAYING, Stop being lazy!

Mike! Give us an update man!!

We shoudl be seeing this kind of stuf fin your code, as we had to custom build to get proper APi functionality... but alas, you still do not have this type of functionality!


public function create_item( $request ) {
$params = $request->get_params();

$url = Helper::get_data( $params, 'url', '' );
$title = Helper::get_data( $params, 'title', '' );
$domain = Helper::get_data( $params, 'domain', '' );
$post_id = Helper::get_data( $params, 'post_id', 0 );
$slug = Helper::get_data( $params, 'slug', '' );

if ( ! empty( $url ) ) {
$url = sanitize_url( $url );
}

$data = array(
'url' => $url,
'title' => $title,
'domain' => $domain,
'post_id' => $post_id,
'slug' => $slug,
);

Can you please just document what is available and exactly how to use the API? You can do that in this response for others looking for help as well if you dont want to update the documentation on your website. this is such a powerful and unique feature, it really is the only plugin doing it, so please help and add methods and params!

POST: {{wordpress_url}}/wp-json/url-shortify/v1/links?url=google.com

I tried sending as form data, JSON body, query param, and encoded url query param.

I get this:

{

“code”: “rest_forbidden”,

“message”: “Sorry, you are not allowed to do that.”,

“data”: {

“status”: 401

}

}

• This reply was modified 10 months, 1 week ago by maven1129.
• This reply was modified 10 months, 1 week ago by maven1129.
• This reply was modified 10 months, 1 week ago by maven1129.
• This reply was modified 10 months, 1 week ago by maven1129.

Ah ok. Your plugin page says “Coming Soon”. Do you have any other functionality capabilities or methods / parameters in the API? Any documentation? We’d like to be able to generate, expire, update, etc.

BUMP – when we add parameters in the redirect shortcode, it escapes them in to &, which is not recognized. I need it to send just &. Please help?

– never mind – it works!

• This reply was modified 3 years, 4 months ago by maven1129.

yeah there’s gotta be a way to not kill the site when working with a table of 100 rows. Maybe a paged data viewer (wpdatatables – yuck – but they have solved it)

Thanks Tobias. While I was trying my first table import, I loaded about 3000 rows, and the plugin bogged down my admin and eventually the page crashed. I think because it is by default trying to load every row in the json response. Is there something I can do to prevent this?

Wow! Amazing support and thank YOU for the thorough, comprehensive reply. I will give this a go… I didn’t realize that I could put php into the field value field.

Just do it like this? I’d like to wrap it in a “tel:” link as well.

I was always told that I would have to go in an edit each page it was used on, then save it, for the field to update. Are you saying that any time the page is rendered, and this field is present on the page visibility sections, it would update the field that is actually in use on the page, or would I need to also include that hidden field in the content of the page somewhere?

• This reply was modified 3 years, 6 months ago by maven1129.
• This reply was modified 3 years, 6 months ago by maven1129.

I appreciate you confirming that it doesnt support this currently, but my question is how do we add that support? I think it’s a good change and should be much simpler for you to implement as an option in the plugin that me trying to add something in code, but if you can point me to what would need to change to register that for this post type, that could suffice. Mind helping out?

That’s what I’m saying – the link it goes to is: https://domain.com/faq/faq-post-slug/?faq-category=faq-category-slug. That just reloads the current page. Please explain what needs to be done to link to a page that has the category listings page instead: https://domain.com/ufaq-category/faq-category-slug/.

As it sits, the plugin does NOT redirect to that https://domain.com/ufaq-category/faq-category-slug/, but instead, clicking on the category link goes to https://domain.com/faq/faq-post-slug/?faq-category=faq-category-slug. What exactly do I need in place to make the handler for ?faq-category=faq-category-slug go to https://domain.com/ufaq-category/faq-category-slug/
?

Thanks for the rapid support here. Is there a reason for the use_soap parameter for the linked function?