I keep having a re-occurring problem with the 'Plants for the Future' website, I search (using simple parameters) and I keep getting an error website. I read around regarding the error and a number of people seemed to suggest it was a website problem, the the website was simply out of data, so I left it until today (the 2nd) so it would at least be the start of the month and the same problem occurred, is this a known issue?
I only have a small garden so i've been looking for a heavy-fruiting plant for the 'Shrub' layer (which will probably end up being the biggest layer in my garden, short of a lonely Hazelbert) but the problems with the PFAF are causing me some difficulty, can anyone suggest another site as simple to use preferably which would also allow me to search native British species? (i'm in the Midlands of England).
I do hope this is the right subforum, apologies if i'm posting here in error.
Can you tell us the parameters you used that led to a glitch? Then others can try those exact parameters and see if they get a problem.
In general I've had zero issues with PFAF, so my guess is that it's something about your particular setup (browser, browser settings, internet settings, etc.) but the only way to be sure is to have someone else try exactly what you've tried.
M D Scott
posted 2 years ago
Many thanks for the message, basically i'll keep the parameters, pick '5' for edibility and Zone 6 and 5 for the UK habitability search and it seems to work once or twice, then if I go back and change the parameters, maybe 5 for edibility and 5 for medicinal, I get;
"Server Error in '/' Application.
Object reference not set to an instance of an object"
I'm wondering if its something i'm doing, maybe my parameters need to be slightly more specific? It seems strange to get this sort of error message though.
Location: Western Massachusetts (USDA zone 5a, heating zone 5, 40"+)
It might be that you need to refresh the website between searches to clear your cache of the last search. I've had that happen to me a time or two. It is probably a website software bug, but it could just be something in your setup. Can't hurt to try, right?