Forum Replies Created
-
Posts
-
Hi!
I think it’s not possible in wordpress to make 2 different result pages and make them both work correctly – I’m not familiar with the concept.
You can try to enable the “Override the default WordPress search results page?” option on the General Options -> Behavior panel, but there is a good chance it still won’t work.
Multisite posts are stored in different database tables, so the internal get_post($id) wordpress call is not able to parse them across another site, and I believe that’s why you don’t have any results if the term is outside the site.
Unfortunately I don’t think any solution exists to that yet.Hi!
I can’t seem to access your server at the moment, it looks like it’s down. Your host might be doing maintenance, will try again later.
In the meantime if you have any error logs regarding the issue, it would be extremely helpful. It would probably point me to the problem.
Okays. I don’t have a copy of that plugin, since as I can see I would have to buy it.
I’m sure it’s possible somehow, but I need to know how to programatically get the status of a user. I see two options here:
1. Asking the plugin developer how the profile status is stored, and if there is a method of getting a profile status based on the user ID
2. ..or letting me check your site back-end and code by providing temporary admin and FTP information, where I would examine the UPME code as well, and maybe I can tell how this information is stored.
If I know how to get the profile status, I might be able to put together a short code snippet to solve this.
Hi!
Because there is no option for that yet. WordPress stores all the categories and taxonomy terms on the same table, so it’s extremely hard to make a hierarchy if both taxonomy terms and categories are supported.
I’m working on a release where I was able to solve this on the back-end yesterday, but the front-end is yet to come. So please hang on, it’s going to be possible one way or another. I’m working this weekend as well to be able to release version 4.1, where this should be solved.
Hi!
Could you be more specific what do you mean by inactive? You mean users that didn’t post for at activity feed for long time?
If it’s possible to get the last post date somehow, I guess it’s possible to filter them with a custom code.
Hi!
Drop-downs are only available for custom field selectors, category (or any taxonomy term) selectors are available only as checkboxes.
You can read more about custom field selectors in the documentation: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/frontend_search_settings/custom_field_selectors.html
I guess because multisite support was added later to the specifications list, when I had that custom content search ready. I’ve tested the multisite queries for days focusing on optimizations, but I never thought of that until now.
Okay, thanks.
I’ve tried chrome dev tools switched to iphone 5 screen user agent and resolution, but I don’t get the errors on the console on that url. I don’t have an iphone with me right now so I can’t look with that, and even if I had, I couldn’t be able to see the iPhone error console as I’m not using a Mac computer.
I also tried ipad, ipad mini and iPhone 6 resolutions, but there are no errors.
iPhone 5 test: http://i.imgur.com/ruEBCIL.png
iPhone 6 test: http://i.imgur.com/rfEJRVE.pngI have no idea why is it happening to you.
Hi!
It does not look like a general issue, it seems to me like a 3rd party CSS rule is causing it.
I can only confirm if I can see the at least the front-end.
Looks like some kind of negative margin, padding, position or floating applied to the fieldset element maybe from the theme or anothe plugin CSS?
But that’s just a guess, it might be something else. If I could see the problematic url I might be able to determine the cause.Hi!
I just checked the juice page, and I’m getting no errors in the console, and the plugin seems to be working. Here is my console from the “Juice” category page: http://i.imgur.com/BF7IbKA.png
Have you found the cause?
Hi!
The first line on that error log tells that the main javascript file could not be loaded by the browser because of a “Failed to load resource: connection reset” error.
It happens primary if the apache virtual hosts handler or the .htaccess file handler recognizes a pattern in the request and forwards a different request. In other words there is most likely a misconfiguration in the .htaccess file.
You should also check if the file is accessible directly from the browser.Other causes might be bad permissions or ownership settings, but I don’t think this is the case.
Also, make sure that you don’t have anything in your system “hosts” file ralted to that domain.
Hi!
Sorry about that, I forgot to look at the screenshot. You are right, it wasn’t working.
The bad news is that I never thought of using the custom content area on multisite installs, this is the first time it came up.
The good news is, since you have provided temporary access I was able to make changes to the plugin files and implemented this feature. Please DO NOT reinstall or delete the plugin, the changes will be lost. This is not a final solution, I had to improvise to make it work for you, so please rather do not use it on your other sites.
I will definitely create a permanent solution for the upcoming version, so no worries about future upgrades.
Hi!
Yes, it was actually a misconfiguration, but I didn’t spot it right.
The Override content? was enabled on the General Options panel and it was set to custom content. That’s why it didn’t find anything. After turning this option off the plugin works again.
Currently I have turned off everything on the layout options like you had it before.
The documentation covers most of this.
First you have to create a search instance for that: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/getting_started.htmlThen you can access the search settings: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/general_settings.html
As well as the multisite settings: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/multisite_settings.html
Hi!
Yes, the problem is that autocomplete in the current version uses an internal method (which should be faster) than the search itself – but only later I discovered that it does not take WPML language into account for some reason.
I have already fixed this, but unfortunately I can’t provide a quick fix to this issue because it affect multiple files. The new version is close to release (3-4 days tops) so I suggest turning off this feature until then. Sorry about that.
