Migrating PHP/MySQL Application to Website Baker

[NorHei]

I would use code2 for a fist try, as it has PHP, HTML and JS blocks available.

Another idea would be to use a wrapper.

[pcwacht]

if your php code etc works

try code section, in it paste your code
Make sure not to use the php tags
html etc should be echoed

Other option
make a module, your code should go to view.php

Good luck,
John

[edsontkasai]

hey, whats up...

please help-me!

I wanna get some datas of the mysql, and make one list with somethings datas,
but I dont use modules for this case, I used the module MPform for create the table of datas,
now I want get the datas createds from MPform and use on the new other page creating my list,

att,

[hancman]

Hi there,
I am about to migrate an PHP/MYSQL application to website baker and need just a little advice.

The php pages are all structured as follows:

Block 1
[
PHP CODE processing form submits
]
Block 2
[
MIXED HTML/PHP/JAVASCRIPT

e.g., HTML/PHP -
<textarea name="SessionNotes" cols="40" rows="6">
<?php echo htmlentities($row_rsCaseManagementSession['SessionNotes'], ENT_COMPAT, 'utf-8'); ?>
</textarea>

e.g., HTML/JAVA SCRIPT/PHP
<td>
      <script>
      DateInput('SessionDate', true, 'YYYY-MM-DD','<?php echo      htmlentities($row_rsCaseManagementSession['SessionDate'], ENT_COMPAT, 'utf-8'); ?>')
      </script>
</td>

]
[
PHP CODE releasing database resources e.g. mysql_free_result statements;
]
the form action parameter uses "<?php echo $editFormAction; ?>" to use Block 1 to process the form submission.

I suppose Block 1 could simply be put in an independent php file and use the action parameter to access it.
Is that a say assumption?

Block 2 is where i really get lost. Since the PHP code is used to dynamically populate form fields and the other code address form formatting and behavior, i am wondering is there any straight forward way of dealing with the code as a group vs. having to develop individual snippets for each piece of PHP needed?

Any suggestions would be greatly appreciated.

Thanks,
Mike...