Bukkit

OnTime: 3.13.4
Bukkit: 1.7.9-R0.3 (Spigot)

What storage option are you using? (YML or MYSQL) ? changing from YML to MySQL

What permissions plugin are you using? (Groupmanager, PEX,bPermissions, etc.) PermissionsBukkit 2.4

What steps will reproduce the problem?
1. Run with YML database for a while, get players into database, Export YML database, shutdown server
2. Setup MySQL server, enter username, password, database name into config.yml
3. Launch server, confirm that OnTime has no erros connecting to MySQL database
4. /ontime import yml playerdata.yml

What is the expected output? What do you see instead?

There are no players listed in plugins/OnTime/playerdata.yml

Do you have an console log of what happened?

Console log only shows command being executed

Please provide any additional information below.

It appears the import routine can no longer recognize the format of the playerdata.yml file.  If I specify playerdata it clearly can't find that file so it clearly is reading the correct file just it's not in the format it expects.

Would it be possible to get the source on GitHub or by another means, I've already debugged two plugins for the author of RoyalCommands.

Did you follow these steps?

http://dev.bukkit.org/bukkit-plugins/ontime/pages/other-functions/#w-example-moving-from-yml-to-mysql

Found that later.  So this bug report can be deleted.  When you read the commands it seems as through you should be able to import the playerdata.yml file.  I think it directly says you can.  I'll read through everything before I file another bug report, I was rushed for time as this is a live server I was working on.

Yes you should be able to import from the yml file. I was just doing a full regression test on next update out soon, and had no problem getting that function to work.

Did you remember the .yml extension when you specified the filename?

Yes I had the extension .yml, that is why I knew it was trying to read the file because afterwards I tried without the extension and it clearly said it couldn't read that file.

I located the error in the code on the import that was preventing the action. I will have this fixed in next update. Thanks for the report.