Dialogs error

[DungeonMaster]

A constant error when adding a new row the first time via npc_dialog_links and npc_dialogs:

 

Error: Undefined variable: table

HINT: You should always declare your variables before using them. However this error could be triggered as well if you made a typo in the variable name or you missed to call the global $var_name command.

Error in "/modules/admin_edit_tables/content.php"

Line 285

Error in /libs/common.php

Line 554

Error in /index.php

Line 329

When I add the EXACT same input the second time it works.

[jcvenom]

you haven't declared

 $var_name 

so there is no

 $var_name 

in your script what is

 $var_name 

or you probably have a space or number on the start of your variable remember to use a underscore if you want a space and never start your variable with a number you need to have a look. If you don't mind me asking what is

 $var_name 

assigned to?

Edited July 4, 2013 by jcvenom

[DungeonMaster]

It is not my script - it is the default dialogs module that comes with NWE.

This happens with plain text dialogs no extra action code or anything.

[jcvenom]

It is not my script - it is the default dialogs module that comes with NWE.

This happens with plain text dialogs no extra action code or anything.

send me the file or post here

[KyleMassacre]

send me the file or post here

Well since its the table editor I believe that comes with the free version of NWE so you can download the free version and check it out.

Now for the error, I have seen that once before but couldn't figure out what caused it and couldn't replicate it again. I just thought maybe it was a hiccup in script execution.

Does this happen every single time you go to add something through the table editor? If so maybe try reinstalling it with either the install single module or sometimes what I do to make sure I'm getting a fresh install is change the version number to a lower version and updating it that way

[a_bertrand]

First of all thanks for the report and the catch of this odd issue. I managed (with a bit of efforts) to reproduce the error. Basically, if you was using only the side panel to select which table you wanted to edit, this would never be triggered. On the other side, if you added a new row, and then selected another table via the table drop down list selector, you would have nasty effects. Anyhow, I uploaded a fixed version which should resolve this issue (hopefully).

[jcvenom]

First of all thanks for the report and the catch of this odd issue. I managed (with a bit of efforts) to reproduce the error. Basically, if you was using only the side panel to select which table you wanted to edit, this would never be triggered. On the other side, if you added a new row, and then selected another table via the table drop down list selector, you would have nasty effects. Anyhow, I uploaded a fixed version which should resolve this issue (hopefully).

thanks a_bertrand i couldn't find the error