After briefly looking at your code....
For starters You need to put the foreach loop inside of the for loop instead of outside of it.

As is $datas is only going to contain the last copy of the array and you will only load the database with this last entry.

You need to place it inside the for loop in order for you to properly step through all of the entries.

Your foreach loop looks ok otherwise to me but I might be missing something.

You really need to first get your code in the right place and if it still isn't working you need to step through the code.

As zyspec mentioned you also need to make sure the database isn't setup with a unique field because if you keep running your code and you are only seeing one entry this is because you are only updating the entry you have instead of making a new one due to the unique field.

Your first $datas = array(); line is unnecessary because you are doing it a couple of lines later. Although this shouldn't cause any issues as is otherwise.

I also agree with Zyspecs comments about creating the object and deleting it afterwards. Otherwise your object could contain items you don't expect.
Rodney

Rodney's correct... I didn't notice that $datas was only being filled with the latest copy of the array.

You can also accomplish this by changing the following line:


with:

Quote:
Yep, that was I was looking for:


Thanks guys for providing the fix for it. Hopefully Timgno can use it now...

I'm glad of your help, but it did not work either as you say

Meanwhile, I found some very interesting tools:

http://marcelog.github.io/articles/ci_jenkins_hudson_continuous_integration_php_phing.html

And look the modifies:
Admin/fields.php


class/fields.php


I posted all the code so that can see even those who are not registered to the forum and the potential to help

A little help here.. Your code is a little wrong...

A quick primer...


If you do a variable dump should look something like this...

$data {
one = 1
two = 2
}




If you do a variable dump should look something like this...

$data {
array() {
one = 1
two = 2
}
array(){
three = 3
four = 4
}
}

if we took this one step further and did this:


The second $data replaces the first and you get a variable dump that looks like this:
$data {
three = 3
four = 4
}

Note the difference..

In this most recent variation of your code every time you go to the foreach loop you will step through each element of the $datas variable that has been loaded and you will send a large array of all of your key/value pairs to the setvars.

The fix SHOULD be simple... Just remove the $[] from the $datas[] line.

I had thought to suggest the $datas[] suggestion until I realized how the code was running.

By adding the [] you are creating a 3 dimension array...
Without it you are doing a 2 dimension array.

I BELIEVE then you will step through each key/value pair and send this to setvars and SHOULD work. Assuming that setVars can accept an array.


In brief I think it is getting made more complicated than it needs to be. The original post should have worked just by moving the foreach loop within the for loop.

But again, this type of bug can be figured out by doing a series of variable dumps at different stages and looking at the value. This is a coding issue and not a database issue.

I do not have time to run this code at this time but I should be reasonably accurate.

Rodney

You were very explanatory Rodney, but I think we should Work it yet to find a solution.

In the previous versions of this module, it was easy to put in a textarea all fields in a table.

I wanted to separate them because, as seen in the image of a previous post, there are icons on the cross, just in the right place to insert the object you want to appear on the form when we're going to create it in our class.

For example, in previous versions it was all so that was created based on how the code was written in the file creators.

With this system, the same as the model system block in admin that you can move in different places, this can also move an object to where we want it.

I hope was clear

Also entering the separate fields from the tables, these are more readable in the database in case of changes or views

Quote:
We've been using them already in the development of XOOPS 2.6.0, thanks to hard work by Alain91. See this news and look for the part about Jenkins.

And you and I had many emails about testing tools like PHPUnit and Sahi

But there are new tools that we're starting to use, and there will be soon a separate article about it

Quote:
As I suggested earlier, the best way to see what is wrong is to debug it, i.e. to set a breakpoint and check the status of the variables. Then you can see if your logic is correct and you have what you expect.

That's what I did, and it seems that your issue is that the "$table_nbfields" variable is empty at the point when you get to this code:



so this:


will never be true and you will never get to the code that you have shown us. And of course, you will never be able to test any changes you are making to it.

You define the variable as:

But there is no variable of this name in the $_REQUEST.

There is the "field_numb", which seems to be the one that you're should be using.
Fix that, and then you'll be able to see if the whole array issue is working or not.

Always check your logic to make sure that you are getting what you expect to get, and that's why tools like PHPUnit are so helpful

It's true

I run a dump of the variables:

I find this result:


The functions that I use for the requests are as follows:

OR


The result is always the same

You need to go step by step backwards.

You want to assign a sanitized value of "table_nbfields" from $_REQUEST:


But "table_nbfields" is not there. So you need to find out why it is not there, by finding the place where you are setting up this variable to "get" or "post".

The logic errors are the worst, because the syntax might be correct, and you won't get any PHP errors or warnings, but the result is still wrong. So go back through your logic step by step, set up breakpoints on the way to make sure that the variable is still there, and with the correct value. Then move to the next step...

This is one of the best and most funny pictures about debugging: