listing preview problems need help asap
This topic contains 33 replies, has 4 voices, and was last updated by  Stiofan O’Connor 7 years, 8 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket- 
		AuthorPosts
- 
		
			
				
February 6, 2018 at 5:34 pm #416297Could you turn off GD Booster while we take a look at this? Let me know February 6, 2018 at 5:45 pm #416299Hello, I was able to recreate the issue by seeing that, when I added a value to the Online Bid field, the preview page became blank. Flagging this for the developers to take a look. February 6, 2018 at 6:24 pm #416308The post field for the url is “geodir_proxi” i am guessing the server has a security rule to chck for post fields with “proxi” in it. The server is returning Status Code:406 Not AcceptableYour server admin should be able to check the server logs and tell you why. Thanks, Stiofan February 6, 2018 at 10:19 pm #416323I will have a look and maybe change the name associated with it. You maybe correct with the name. Thanks for having a look. I will update later if changing the name works or not. February 7, 2018 at 12:45 am #416330SUCCESS!!!! 
 I simply renamed the field in all areas it was called and it worked.
 Thank you again for the Top Notch Support…..So note to self dont use proxi in any field name lol RESOLVED!!!!! February 7, 2018 at 1:20 am #416334ok well not so fast lol.. 
 seems it will only work for one listing then same issue happens.
 I am going to continue to test.
 Any insight on this….February 7, 2018 at 4:04 am #416362Ok I am at a loss… 
 Why can someone enter a website url in the website field that is not a custom field and it be ok.
 But when you add a url in the custom field I created it doesn’t work.
 Also If you enter my domain in the custom field I created it works.
 But any other url it doesn’t….Very Strange…. February 7, 2018 at 4:43 am #416367This reply has been marked as private.February 7, 2018 at 5:35 am #416381This reply has been marked as private.February 7, 2018 at 6:16 am #416394Please post the logs for review February 7, 2018 at 6:18 am #416396I don’t know what you mean as far as logs. I don’t have any to post. February 7, 2018 at 6:25 am #416399Then please contact your host, as Stiofan mentioned here: https://wpgeodirectory.com/support/topic/listing-preview-problems-need-help-asap/page/2/#post-416308 February 7, 2018 at 6:29 am #416403I did and there is no fix with them. 
 Why can a user input a url in the website field and there is no issue. But when a user inputs a url in a custom url field it gives a blank listing preview.
 Do you have any thoughts?February 7, 2018 at 6:42 am #416408This reply has been marked as private.February 7, 2018 at 11:00 am #416444Hi Kevin, I know how frustrating something can be when something does not work 🙂 Let me explain the situation a bit more clearly and what i think is going on. 
 When it does not return the proper preview the server is returning the code 406 (Not Acceptable) instead of 200 (OK), this seems to be a server level error. We have seen similar things in the past with certain names for fields and in most cases the is a mod_security rule on the server, mod_security is a sort of server firewall that has many security rules that prevent actions if it thinks it might be a hack attempt. I myself have had to disable many rules for customers on my server over the years because of false positives.Now your server admin should be able to looks at the server logs and it should tell him something like mod_security rule 12345678 triggered at date XYZ, he would then go and disable that rule 12345678. To test this theory, you can try changing the names for any custom fields u are having problems with to something generic like “field1, field2 etc…” (though the server might be blocking the “http” part of the value). In short this is not something we can fix, it needs to be fixed by a server admin (try googling server code 406 mod_security) Please let us know how you get on. Thanks, Stiofan 
- 
		AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket