also noticed something funky is going on with search, if you click the text area to enter a search term it pops a warning no search text entered almost like it is activating the search button, am noticing it here as well as my own site.

I will have to leave this to Steve or Andy, but in the meantime I agree I’m seeing the same warning text when clicking in the search box, very odd..

Thanks for letting us know!

afraid I dont have much of an idea on the filemtime one…  its a standard php function and throwing error trying to look at date of your file… does the file exist on your server?  think you would have bigger issues if it didnt…  its when its trying to see if it needs to create the js cache…

as to search, mighty odd…  saw that a week or so ago, but it had cleared up… some how its back… 🙁

search does work fine, you just get that extra notice…  will have to see if I can figure out what is causing it…

yes the file is there

the search box issue is a class naming conflict…  unfortunately, the same class name is used in two spots… and a js event handler was added to the class to catch the clicking on one of them… but its gonna catch both…

super simple fix… except its in js…  so not really sure how to get you a patch to remove the error…  might be able to attach a zip file here with the three files… or consider some other options…

we are still researching the other one, but not seeing similar error…

can you try something for me?  on the line you have errors for filemtime, can you make small code change?

so change

                @$js_m_time = filemtime($js_relative_url); # getting the mofified time of the js file. extracting the file's dir

to

                $js_m_time = @filemtime($js_relative_url); # getting the mofified time of the js file. extracting the file's dir

it just moves the ‘@’ around… 

then on forum – toolbox – error log, clear the error log…  then on forum – toolbox – housekeeping, clear the combined js cache…   go visit the site…  go back and check the error long…  still there?

Will give it a shot later this evening or in the am

okay, just let us know…  The @ is supposed to suppress errors… but it really should be on the function, not the variable…

Tried it and it didn’t work, did the update and it seems to have fixed it, just getting this notice now

file: /simple-press/sp-api/sp-api-plugins.php
line: 837
function: sp_combine_plugin_script_files
Notice | Undefined index: js-spgroupview

Can you turn off the js cache in the options – run a few pages- and then turn it on again?

Although check your version as you do need 5.6.3.1 which we made available yesterday.

that seems to have done the trick!

Now that’s what I like to hear 🙂