Forum Replies Created
-
Posts
-
Hi!
Sorry, I had a business related stuff to take care of today.
If you transfered over the exact files, the fix should be there. Just make sure that the Javascript Source is set to “Non Minified” on the Compatibility settings submenu. The transfer might have changed that back to the default value.
The change I did was the following:
– Open the wp-content/plugins/ajax-search-pro/js/nomin/jquery.ajaxsearchpro.js file
– Then after line 72, which should be this:[code] $this.lastSuccesfulPhrase = ”; // Holding the last phrase that returned results[/code]
I added the following line:
[code] $this.o.redirect_url = $(‘<textarea />’).html($this.o.redirect_url).text();[/code]
I just checked via FTP, the line is there, so it’s probably only the compatibility option changed.
Hi!
Can you please be more specific? There is an option to trigger the search if the user clicks changes the checkboxes or any settings, but I’m not sure if that’s what you are looking for.
Hi!
If I understand correctly, you want to open the only the custom URLs in a new window. Well, there is an option to open all links in a new tab on the Layout Options -> Results behavior panel. (first option)
First of all, enable that option so everything is redirected to a new window.
Then, try using this custom Javascript method:
[code]
$(function() {
$(‘.results’).on(‘click’, ‘.asp_isotopic_item’ , function(e) {var thisDomain = "offthestreets.co.uk";
var url = $(‘.asp_content > h3 > a’, this).attr(‘href’);// If it is a local url, prevent opening a new tab, open directly
if (url.indexOf(thisDomain) > -1) {
e.preventDefault();
e.stopPropagation();
location.href = url;
}return true;
});
});
[/code]It basically attaches a function to the click event of the result item. Then checks if the item url is local or not. If local, then aborts the default operation (opening to a new tab) and instead it opens to the local window. Not sure how this is going to work, but this is the best idea I can think of, which does not include modifying the plugin code.
Hi Daniel!
I see the problem, but I have no idea what is causing it. It’s most likely a 3rd party plugin or theme issue. Basically some part of the configuration string is html encoded and the plugin script is not able to read it. Something is encoding it, but unfortunately I can’t tell yet.
I’ve tried to log-in with the details give, but I’m getting a redirect loop error: http://i.imgur.com/7n2KEn7.png
Can you please check the login data on an empty browser to see if it’s working for you?Also, I will definitely need temporary FTP acces to find the cause and fix it if possible. This is an unknown issue yet. You can safely add FTP details by editing your initial post in this thread, or by uploading a .txt file with the details. Both methods are safe, visible only for me and you.
I think I might have a solution for the text shift. It’s the placeholder styling causing it. Most likely the theme, I’m not sure, the inspector does not show these styles unfortunately.
Try this custom CSS:
[code]input.orig::-webkit-input-placeholder {
line-height: 24px !important;
}input.orig:-moz-placeholder { /* Firefox 18- */
line-height: 24px !important;
}input.orig::-moz-placeholder { /* Firefox 19+ */
line-height: 24px !important;
}input.orig:-ms-input-placeholder {
line-height: 24px !important;
}[/code]That should fix the line height issue 🙂
Thank you for your kind words!
Later today I’m going to test from another PC as well, to make sure it’s not mine.
What I also tried is to run chrome fully without extensions. You can do that by creating a .bat file and putting this as content:
[code]
taskkill /F /IM chrome.exe
taskkill /F /IM iexplore.exe
taskkill /F /IM googleupdate.exe
taskkill /F /IM outwit-hub.exestart chrome –disable-extensions
[/code]This will make sure it’s not an extension causing the bug. I’ve looked through the internet, but I haven’t found any focus related issues with input fields on chrome. The same code is used for every browser.
I’ve tested windows 8 and 10, 64bit, I don’t have a mac unfortunately.
Browser: Chrome Version 45.0.2454.101 m
Maybe some browser extensions?
Hi!
1. With a negative margin custom CSS, something like:
[html]
div[id*=ajaxsearchprores] {
margin-top: -35px !important;
}
[/html]2. The console reports that the Advanced Ajax Page Loader compatibility is enabled, but the plugin is not used. If you deactivate it on the General Options -> AAPL panel, it will work again.
Yes I did, it behaves the same for both Chrome and firefox to me.
Video test, chrome: https://vid.me/mUEg
Video test, firefox: https://vid.me/F7O6
In neither of the videos did I had to click on the input field, it stayed focused.
I fully understand your point, and I wish this was easier to me as well. I can try explaining how it’s done,
1. To create such complex forms, first of all you will have to create and use custom fields. If you are not familiar with them, you can read more in the wordpress codex.
In very short: Custom fields are basically data fields attached to a post or page or a custom post type (like a product, or forum topic). Each and every custom field has a name and a value. The article I linked above will explain how you can create such custom fields.
2. Once you understand how custom fields work, and you maybe created a few for testing, then you can proceed to create the search fields as seen on the TV demo. There is a chapter in the documentation you should read through, which explains fully how you can create these fields: https://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/frontend_search_settings/custom_field_selectors.html
The basic concept of this is, that you can create various items (radio buttons, checkboxes, sliding bars) for any selected custom field.
Let’s take the TV size slider as an example:
– First I created all the TV products I wanted.
– Then I opened the first one an added a custom field called “tv_screen_size” and as the value I entered 50. Screenshot.
– I repeated this process for each and every TV product I created. The screen sizes were different for some of them of course.
– Then when I was done entering the fields, I created the range slider on the search options page as following: http://i.imgur.com/w6VS65I.png
– Hit the blue SAVE button on the editor, then the Save All tabs button.
– The range slider should be now visible on the front end.To add more and more different selectors, just repeat this process.
I’m sorry if something is not clear, it’s very hard to explain as the developer as I might see this differently from a customer.
Let me know if you need any more help.
Hi!
I’m working on video tutorials on how to create more complex forms, some of them should be available this week 🙂
You can use the upper mentioned code in any post or page.
Hi!
Does the problem still persists? Can you provide temporary access where I can check on the problems?
Hi!
Can you be please more descriptive? I tried typing, waited for the ajax request and the focus stayed in the input field. Is that the problem, or something else?
Hi!
This sounds more like a theme issue to me. The redirection seems to be correct after typing in the “plages 2”, I’m redirected here: http://www.playas-valencia.com/fr/?s=plages%202
After a few try I got a fatal error which states the following to me:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 6 bytes) in /home/content/p3pnexwpnas07_data01/81/2662781/html/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 5061
This means there is not enough memory left for WPML do do something, that is not disclosed in the error message exactly. The cause might not be WPML, but I’m definitely sure it hsould not run out of memory ever.
You can try increasing your memory limit, that usually helps. You can try higher values like 256M or even 512M if the values in the article are not enough.
