[Ernest Marcinko]

Okay, I think I found it. So I googled a bit, and it seems like that each placeholder must have a separate rule, otherwise it won’t work. Strangest thing I have ever seen. So the final solution is:

[code]
@media only screen and (max-width: 980px) {
input.orig{
font-size: 12px !important;
line-height: 15px !important;
}
input.orig::-webkit-input-placeholder {
font-size: 12px !important;
line-height: 15px !important;
}
input.orig:-moz-placeholder {
font-size: 12px !important;
line-height: 15px !important;
}
input.orig::-moz-placeholder {
font-size: 12px !important;
line-height: 15px !important;
}
input.orig:-ms-input-placeholder {
font-size: 12px !important;
line-height: 15px !important;
}
}
[/code]

[Ernest Marcinko]

You can edit the first post in this thread and add the private details, or upload a txt file with them. Both are safe, and visible only for me and you.

[Ernest Marcinko]

I have no idea, the rule seems to apply correctly as the inspector tells. It doesn’t seem there is anything conflicting either. I just tried on my test environment, but I was able to change the placeholder text with that rule.

Do you have an url where I can see this?

[Ernest Marcinko]

Hi!

I think the placeholder text needs a different rule for CSS3 supported browsers.

Try something like:

[code]
@media only screen and (max-width: 980px) {
input.orig,
input.orig::-webkit-input-placeholder,
input.orig:-moz-placeholder,
input.orig::-moz-placeholder,
input.orig:-ms-input-placeholder {
font-size: 12px !important;
line-height: 15px !important;
}
}
[/code]

[Ernest Marcinko]

Hi!

Here is a documentation chapter about safe-updating.

It’s basically a re-installation of the plugin.

An auto updater is coming soon, once there will be a solution to avoid auto-updates on pirated copies 🙂

[Ernest Marcinko]

Hi!

The only thing I can think of is caching or grouping. The code looks all right to me as it is, and it definitely should work.

Is the results grouping or caching enabled by any chance? For grouped results this code won’t work.

As for the second request, the only possible way I see is to edit the results template file to a similar structure and add corresponding CSS as well. Here is an knowledge-base article explaining how to do that. I only recommend editing these files, if you are falmiliar with PHP, HTML and CSS programming.

[Ernest Marcinko]

Hi!

It indicates that the ajax response body is empty, so there might be an error there, but it’s not displayed. Can you turn on the error reporting in the wp-config.php file? I will try it again, maybe it will display something informative with the error reporting.

Once again I see the extremely long cache control headers. This very long string is sent to the server:

no-store, no-cache, must-revalidate, post-check=0, pre-check=0, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache, no-cache

The search plugin does not modify the ajax header. This might not be related to the issue at all, but it’s worth investigating where it’s coming from. Something, somehow is adding this extra overhead to the ajax header.

[Ernest Marcinko]

Hi!

I’m sorry, but unfortunately I can’t accept customization requests.

[Ernest Marcinko]

Hi!

I’m not sure which plugin version are you using, but the current one (4.5.1) has a new feature called “Index table engine”. It was designed mainly for databases with high record counts, to minimalize the SQL query CPU needs.

There are 4 new chapters in the documentation about the index table usage, you can check them out.

Also, there are 3 performance tuning chapters in the documentation, that will definitely help you optimizing the plugin performance.

To safely update the plugin, please read the important update notes.

[Ernest Marcinko]

Hi!

The results page translation you are referring to is part of your current Theme, not the search plugin. I think you will find it somewhere in the search.php file in your theme directory.

It should show the same amounts of results on the results page, like on the ajax list. Make sure you have the Override the default WordPress search results page? option turned on the General Options -> Behavior panel. That way the plugin will try to override the default result list, with the ajax result list.

[Ernest Marcinko]

Hi!

Yes you can. On the General Options -> Sources panel, click turn on the Search in terms? (categories, tags) option on the bottom of the page. That way the search will search the terms related to the posts, but still return the posts.

[Ernest Marcinko]

Hi!

I think I might need FTP and back-end access to check on this issue, as there is no error message shown on the screenshot, and I have never seen an issue like this before.

A few questions though:

• Is this only happening on the index table options page, or everywhere?
• Have you tried disabling all of the plugins and switching the theme? This is the only way to make sure it’s not a plugin/theme conflict.
• Is the error reporting enabled in the wp-config.php file?
• Have you deactivating, deleting, and re-installing the plugin?
• Have you tried a different browser? What browser are you currently using?

It looks if like if the HTML code is not rendered, or completely stripped from HTML tags, or unfinished for some reason. I would say it’s a 3rd party javascript stripping the tabs content from the HTML tags, and only showing the plain text, but it’s only a guess.

[Ernest Marcinko]

Hi!

If the normal description is showing, then the “if ( $checkboxes ) …” part of the code is not executed. I think the ACF get_field() function needs a post ID as well. Try this modification of their suggestion:

[php]
add_filter( ‘asp_results’, ‘asp_checkbox_to_results’, 1, 1 );

asp_checkbox_to_results( $results ) {
foreach ($results as $k=>$v) {
// Get the field
$checkboxes = get_field(‘my_checkbox_list’, $v->id);
// Append if exists
if( $checkboxes ){
$checkbox_string = implode(‘, ‘, $checkboxes);
$results[$k]->content .= " – " . $checkbox_string;
}
}

return $results;
}
[/php]

• This reply was modified 10 years, 9 months ago by Ernest Marcinko. Reason: fix

[Ernest Marcinko]

Nice. First of all you need to change back the Advanced description field option to the default {descriptionfield} because we are doing a different solution.

Then, I put together a filter, which parses through each result and gets the ‘my_checkbox_list’ field as per suggested on ACF support forums. Then it’s appended to the description:

[php]
add_filter( ‘asp_results’, ‘asp_checkbox_to_results’, 1, 1 );

asp_checkbox_to_results( $results ) {
foreach ($results as $k=>$v) {
// Get the field
$checkboxes = get_field(‘my_checkbox_list’);
// Append if exists
if( $checkboxes ){
$checkbox_string = implode(‘, ‘, $checkboxes);
$results[$k]->content .= " – " . $checkbox_string;
}
}

return $results;
}
[/php]

Hopefully it will work.

[Ernest Marcinko]

Hi!

Sorry for the late answer, I’m getting lots of tickets due to my vacation last week.

I’m releasing a bugfix update today regarding a few bugs, including the visual composer problem as well.

Let me know if there is anything you cannot resolve.

[Author]

Posts