Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting Up WebApp #42

Open
MarcusGHub opened this issue Jun 26, 2023 · 7 comments
Open

Setting Up WebApp #42

MarcusGHub opened this issue Jun 26, 2023 · 7 comments
Labels

Comments

@MarcusGHub
Copy link

MarcusGHub commented Jun 26, 2023

Screenshot_2
Screenshot_1
This is more of a request to assist in setting up the web app.

I have setup my webserver and loaded the mmex web app. I am taken to the page to enter password and username, but there's no save button to saving the settings. Am I missing something?

Where do I find the GUID of the desktop application? GUID is blank on the web app.

@MarcusGHub
Copy link
Author

@vomikan can you please help?

@luisdev
Copy link

luisdev commented Jun 27, 2023

I think I had the same problem. This is a workaround, not a fix, but I ended up manually creating the MMX web config file when I origionally setup the WebApp.

Do you have a configuration_user.php file on your MMX server? If you do, edit that file and put your MMX username and password in there. It should contain variables like this:

$disable_authentication = "False";
$user_username = "your_db_username";
$user_password = "your_db_password";
$disable_payee = "False";
$disable_category = "False";
$defaultaccountname = "Your account";
$desktop_guid = "{12A3456-ABC1-AA00-1234-0012E345AA6X}";

Update the username and password fields with your data. Save the file on your server and then load the MMX index.php in your browser.

@vomikan
Copy link
Member

vomikan commented Jun 27, 2023

I used docker. Therefore, I am not familiar with such a problem.

@MarcusGHub
Copy link
Author

MarcusGHub commented Jun 29, 2023

I think I had the same problem. This is a workaround, not a fix, but I ended up manually creating the MMX web config file when I origionally setup the WebApp.

Do you have a configuration_user.php file on your MMX server? If you do, edit that file and put your MMX username and password in there. It should contain variables like this:

$disable_authentication = "False"; $user_username = "your_db_username"; $user_password = "your_db_password"; $disable_payee = "False"; $disable_category = "False"; $defaultaccountname = "Your account"; $desktop_guid = "{12A3456-ABC1-AA00-1234-0012E345AA6X}";

Update the username and password fields with your data. Save the file on your server and then load the MMX index.php in your browser.

Thank you!

I made some progress.

Nothing happens when i enter my password on the web. The error.log file does not show anything for this action.
When I reopened the desktop application and clicked refresh webapp, i get the errors below in the error.log file:
PHP Fatal error: Uncaught TypeError: sizeof(): Argument #1 ($value) must be of type Countable | table|array, null given in /var/www/html/web-money-manager-ex/WebApp/functions_database.php:347\nStack trace:\n#0 /var/www/html/web-money-manager-ex/WebApp/services.php(43): db_function::payee_insert_json()\n#1 {main}\n thrown in /var/www/html/web-money-manager-ex/WebApp/functions_database.php on line 347
[Wed Jun 28 22:10:17.088136 2023] [php:warn] [pid 1697] PHP Warning: Trying to access array offset on value of type null in /var/www/html/web-money-manager-ex/WebApp/functions_database.php on line 340

@MarcusGHub
Copy link
Author

Switched to the docker implementation and all seem to be good now.

@thenotec
Copy link

I installed the webapp in an apache server and i was having this problem too. In my opinion it seems to be a bug in the programming of the latest version 1.2.2. To work around the bug I first installed the old version 1.0.4. Once I set up everything, I then updated to the latest current version and everything works.

@vomikan vomikan added the bug label Aug 24, 2023
@danielfdsilva
Copy link

I had the same problem as listed here just last week.
In my case the sqlite extension was not enabled by default and I believe apache did not have write access to the folder, so be sure that these are fixed.

You don't get the Save button because php kills the script on error and since this is a production deploy, the error output is disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants