hamsn

I think there is a bit of confusion since whatever I wrote in HTML format is rendered in the output form, I wrote & amp ; but it is showing as & here.

Let me rewrite it:
I tried doing the other way round, meaning create the record itself with & amp; instead of just & so when I search in the frontend with & it will output as html & amp; and it would match the record. Only downside is when the record is displayed, it will be displayed with & amp;. But when saving the record it doesn’t save it as html, it saves just as &.

And I didn’t understand what you said, probably even you can use a space in between like this: & amp; to differentiate between html code and the ampersand itself.

And let me know how do I reproduce and make it work.

I tried doing the other way round, meaning create the record itself with & instead of just &so when I search in the frontend with & it will be output as html & and it would match the record. But saving the record it doesn’t save it as html, it saves just as &

Any suggestions?

Well I am using the beta version right now. I am using the same way I used the 1.5 version before, haven’t found any problem yet, still testing it, but I can’t get to see records with “&” or any other records for that matter which have a symbol like ampersand or hyphen.

Alright I understand. Can I join the beta testing and get my hands on it? I will also help you out testing it if that’s what you are looking for.

Let me know.

Alright, keep up updated, thanks.
I don’t know if you want to close this thread, but as you think is appropriate.

Thanks!

Regarding the clear button, even after updating the behavior was same, wasn’t it updated in the version 1.5.4.2? I updated today. But once I disabled AJAX, both the problems got solved.

Thank you so much!
That’s pretty much all!

Yes, when I load the page I see the message “Record not Found” being generated by the single shortcode. But when I enter the keyword and press on search, the “Record not Found” disappears and the list appears. So I think the search is generating it from somewhere?

There’s only one shortcode being used. Even if I use the few lines of code as provided on your website, I still get the same behaviour, so I suspect it is related to the search shortcode somehow?

This is my shortcode in WP: [pdb_list search=”true” template=”single” suppress=”true”]

Regards.

Edit: Further, after I enter keyword and press on search, I get the list of matching results, now if I click on the Reset button on search form, the keyword is cleared and all the records are visible, this thing overrides the filter=”id=0″ or suppress=”true”, so I think the best option would be to hide the Reset button, where is the code for search form where I can edit that out?

Yes, the template is being used for sure, as it is able to hide the drop-down, this is the template code:

<?php
/*
 *
 * template for participants list single record output
 *
 */
if (is_array($this->records)) {
  $id = key($this->records);
} else {
  $id = '';
}
?>
<div class="wrap <?php echo $this->wrap_class ?>">
  <a name="<?php echo $this->list_anchor ?>" id="<?php echo $this->list_anchor ?>"></a>
  <?php
  if ( $filter_mode != 'none' && ! $filtering ) : ?>
  <div class="pdb-searchform">
    <div class="pdb-error pdb-search-error" style="display:none">
      <p class="search_field_error"><?php _e( 'Please select a column to search in.', 'participants-database' )?></p>
      <p class="value_error"><?php _e( 'Please type in something to search for.', 'participants-database' )?></p>
    </div>

    <?php
			$this->search_sort_form_top(); ?>

    <?php if ( $filter_mode == 'filter' || $filter_mode == 'both' ) : ?>

    <fieldset class="widefat">
      <legend><?php _e('Search', 'participants-database' )?>:</legend>
	<input type="hidden" name="search_field" value="client_name">

      <?php $this->search_form() ?>

    </fieldset>
    <?php endif ?>
    <?php if ( $filter_mode == 'sort' || $filter_mode == 'both' ) : ?>

    <fieldset class="widefat">
      <legend><?php _e('Sort by', 'participants-database' )?>:</legend>

      <?php
      $this->set_sortables(false, 'column');
      ?>

      <?php $this->sort_form() ?>

    </fieldset>
    <?php endif ?>
  </form>
  </div>
  <?php endif ?>

  <!-- showing record ID <?php echo $id ?> -->

  <div class="list-container" >
    <?php echo do_shortcode('[pdb_single id=' . $id . ']'); ?>
  </div>
</div>

Even if I use the few lines of code available on https://xnau.com/showing-a-search-result-as-a-single-record/ I still get to see the list, no idea why.

Thanks for your time.

Thank you for replying.
That will solve the hiding of the dropdown.
But regarding the displaying single record, it still appears as a list rather than the record itself upon search. What am I missing?

Your help is appreciated, thank you.

I closed the first error, it was missing an endif. But the search is not functional, something wrong with the code.
Moreover if I simply use the code from here https://xnau.com/showing-a-search-result-as-a-single-record/ and using the qualifier for the statement to suppress the warning, I still get the usual link to the record, and not the record itself.

Basically I have 2 concerns, one is that I want to implement this https://xnau.com/showing-a-search-result-as-a-single-record/
and secondly I want to hide the dropdown.

Please help.

OK, it was due to htaccess file generated by Better WP Security, since it was in root, this folder installation was also getting affected. I just renamed my root htaccess file for time being and everything worked.

Thank you esmi ??

Thank you for your response.
Hopefully you did go through the webpage. I did try reuploading it.
I have uploaded the zip files of wordpress 3.4.1, 3.5, 3.5.1, and I extracted one by one and multiple times as well, but still the issue is same. And I did contact my host to know if they have made any changes in the server script or something, but they said nothing as such.

So let me know what this issue could be. The file exists and also the permissions are there intact, but still I don’t understand the not_found thing.

Thanks again.