Hey @bypr.nils,
The warnings seem to be at different lines compared to the latest version… What version of the plugin are you using?
Thanks~
Which warnings are you refering to? They’re all referencing existing code.
I’m using version 0.5.8 (and wp 3.9.2). The server is running a fairly old php (5.3.29) which unfortunately cannot be updated.
That said, i wanna throw in that i found it a design flaw that you can’t NOT include the database in the dublicate because when applying it you always have to setup a new or delete the old database. Would it be possible to have a third option of update existing database so that it can be left untouched when using a filter?
My bad, sorry for the confusion… I should have just asked you for your version. Basically the error at line 116 was not on the same line as the source this normally indicates an older version but in your case your using the latest…
If want to try the active development version it might have your fixes for the issue your seeing. The very latest version (0.5.9) can be found by following these instructions:
-> Browse to http://wordpress.org/extend/plugins/duplicator/developers/
-> Look for the section “Other Versions”
-> Click on “Development Version” and download the zip plugin file
-> Uninstall your current version and install this one
-> Note: This is a development line version so please test in your sandbox first to make sure you have no issues…
Let me know if this solves your issue. If not you can submit a ticket and I’ll can look closer at your issue if you want…
As far as the 3rd option that is a possibility, the todo list is pretty long right now and this is a free project so including a new dump (UPDATES vs INSERTS) would require quite a bit of testing and its never really been requested by anyone else. I usually try to work on the most requested features since time is quite limited with the plugin, however it has been added to the todo list, so it will get looked at some point in time…
Cheers~
Basically the error at line 116 was not on the same line as the source
But there is a foreach on that line in the file in the latest version, isn’t there? The development version does not help by the way.
its never really been requested by anyone else
That’s strange because it makes the use of the database filter option nearly useless, doesn’t it? Why would you want to create a new database and filter certain tables? Maybe you would want to exclude certain plugin created tables, but you can’t exclude wordpress tables or you’d end up with a non functioning wordpress.
I would have thought that migrating only the wordpress files would be a common usecase since using ftp for big file systems is so painfully slow. But you can’t. You have to include the database. Because the plugin inevitably wipes the database (or creates it new). It could at least check if there is sql included at all, and if not then leave the database untouched (and disable the input form).
But that’s just a suggestion to your otherwise genius addon.
