[Ernest Marcinko]

Hi!

The login is working, thank you. I’m not sure what I should look at, it looks normal to me. Can you please add screenshots or more detailed description of the issue? I don’t know what to look for 🙂

Thank you!

[Ernest Marcinko]

Hi!

I think I have found the source of the problem. Since I cannot overwrite files on your server, please open up the plugins/ajax-searhc-pro/backend/class/blogselect.class.php file and go to lines 24-36, you should see this:

      if ($this->selected!=null && is_array($this->selected)) {
        foreach($this->selected as $k=>$v) {
          $echo = "";
          foreach($this->types as $_type) {
            if ($_type['blog_id']==$v['blog_id']) {
              $_temp = get_blog_details($v['blog_id']);
              $echo = $_temp->blogname;
              break;
            }
          }
          echo '<li class="ui-state-default" bid="'.$v['blog_id'].'">'.$_temp->blogname.'</li>';
        }
      }

Replace that code with this:

      if ($this->selected!=null && is_array($this->selected)) {
        foreach($this->selected as $k=>$v) {
          $echo = "";
          foreach($this->types as $_type) {
            if ($_type['blog_id']==$v) {
              $_temp = get_blog_details($v);
              $echo = $_temp->blogname;
              break;
            }
          }
          echo '<li class="ui-state-default" bid="'.$v.'">'.$echo.'</li>';
        }
      }

It should fix the multisite issue!

[Ernest Marcinko]

Hi!

Can you please provide temporary administrator access? I would like to do a quick debugging if possible, as I couldn’t reproduce the error on my test environment.

[Ernest Marcinko]

Yes, completely.

[Ernest Marcinko]

Yes it does, because the listings site was/is created in the multisite installation, but it’s virtually not the same as the listings site that is actually there.

Managing a multisite needs a bit of practice 🙂 Some plugins and themes are not compatible with multisite, so you should first check if the plugins you want to use on your listings site are compatible with multisite installations.

In my opionion what you need to do is:
1. Backup everything – all the sites, files, databases everything.
2. Delete the public_html/listings directory completely
3. From what I can see from the listings config file the listings wordpress uses the “robborko_wor7” database, you should delete that as well (but first backup of course)
4. Now, log in back to your main site at warwickpost.com/wp-admin and open up the network admin sites panel options
5. Delete the listings site from the sites list – it should be still there
6. Now add a new site – listings
7. That’s it, no files are needed, nothing, if you then go to warwickpost.com/listings url you should see the new wordpress site.

Virtually you will have now a main site and a listings site + a network administrator panel. Some plugins need to be installed through the network administrator panel (such as ajax search pro) some of them not.

It’s a bit hard to get used to it, but as long as you have your backup files it’s going to be all right – you can restore everything if something goes wrong.

Here is a longer reading about this: https://codex.wordpress.org/Multisite_Network_Administration

I hope this will help you a bit with the multisite madness 🙂

[Ernest Marcinko]

Hi!

It looks like those listings are actually posts, which is good. However it doesn’t look like the listings site is part of the network installation, that must be the problem. On the listings ajax search amin page I cannot see any of the multisite instances. It appears to me as the listings site is a fully separate WordPress installation, that would explain why the search can’t find the database entries. The ftp also confirms my theory, as there are wordpress files under the public_html/listings directory, and that directory shouldn’t even exist on a multisite install.

Unfortunately it is not possible to cross-search one WordPress instance from another, the sites must be connected with a multisite installation – this is the reason why you can’t see results from the listings site on your main site.

[Ernest Marcinko]

Hi!

Yes, you should delete those lines even after update, just to make sure 🙂

[Ernest Marcinko]

Hi!

I’ve made some progress with the search, however I cannot access the listings site. I’m also afraid that the listings are not custom post types nor anything similar, which makes them impossible to search 🙁 If you could make a login for me to the listings site I might be able to see if there is anything I can do to make it work.

[Ernest Marcinko]

Forgot the screenshot.

[Ernest Marcinko]

Hi!

I’m just leaving the office, but I’ve noticed 2 things, which should be fixed and will solve some of the issues.

1. I’ve noticed 2 instances of the same search module on the opening page. You should remove one of them, or create another search instance and replace one with that if you want to use 2 searches on the main page.

2. There are number of javascript errors through page loading on my console, which also should be fixed. They are not affecting the search in any ways, however many plugins use the built-in jQuery and one simple error can make them unfunctional. I’ve attached a screenshot of this.

I will take a deeper look at the problem tomorrow morning again. No worries, everything will work fine after a bit of fine tuning.

[Ernest Marcinko]

Hi!

Thank you for the proper description and the login details!
It was a javascript bug possibly caused by another plugin, which I could not allocate. Fortunately I made some changes in the search code, now it should work fine 🙂

[Ernest Marcinko]

Hi!

Thank you for the proper description and the login details!
It was a javascript bug possibly caused by another plugin, which I could not allocate. Fortunately I made some changes in the search code, now it should work fine 🙂

[Ernest Marcinko]

Hi!

The root path was somehow incorrect and the search could not include the wp-load.php file. I’ve inserted the root path manually to the search, now it should work fine!

[Ernest Marcinko]

Hi!

I think I have found the reason. If I’m guessing right, then you had an older version of the search installed, where “Image Precache” was enabled. I left that code in the search in case someone needs it, but it cannot be disabled from the frontendt. Anyways, all you need to do is delete a few lines, and that empty 1,2s ajax request will disappear.

Open up the wp-content/plugins/ajax-search-pro/ajax-search-pro.php file.

Delete lines 232-250:

      if (get_option('asp_precacheimages')!=1) return;
      ?>
      <script type='text/javascript'>
         $(document).ready(function($) {
            function preCache() {
              var data = {
            	  action: 'ajaxsearchpro_precache'  
            	};
            	$.post(ajaxsearchpro.ajaxurl, data, function(response) {
                 console.log(response);
            	}, "json"); 
            }
            preCache()
            setInterval(function(){
               preCache();
            }, 15000);
         });
      </script>
      <?php  

Clear your cache and CDN cache, and you shouldn’t see that long request anymore.

[Ernest Marcinko]

I see 🙂 The problem is that it’s almost on the top of the head tag, and the javascript files are not loaded yet. Try to locate the wp_head(); call in the template header file, and if you put it just under there, it should work then 🙂

[Author]

Posts