ValuAg - Sen, Ara; Toptan, Ayberk; Tufekci, Can: Difference between revisions
No edit summary (change visibility) |
No edit summary (change visibility) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 119: | Line 119: | ||
- We will be working on how to solve a problem that I mentioned above in the problems section. |
- We will be working on how to solve a problem that I mentioned above in the problems section. |
||
- We will create more form pages once we can get data from form fields and |
- We will create more form pages once we can get data from form fields and can put them into the AWS RDS database. |
||
'''Week 5:''' |
'''Week 5:''' |
||
| Line 138: | Line 138: | ||
- We informed our problem to Mr. Dutcher and showed what we have tried and gotten as a result of our actions completed so far. |
- We informed our problem to Mr. Dutcher and showed what we have tried and gotten as a result of our actions completed so far. |
||
- Mr. Dutcher gave us a comment about using LAMP Stack integrated with AWS |
- Mr. Dutcher gave us a comment about using LAMP Stack integrated with AWS to perform data transactions outside of WordPress. |
||
'''Problems: ''' |
'''Problems: ''' |
||
| Line 159: | Line 159: | ||
---- |
---- |
||
'''Accomplishments: ''' |
'''Accomplishments: ''' |
||
- Worked on putting HTML codes on WordPress pages |
- Worked on putting HTML codes on WordPress pages to create form structure. Give unique IDs for every input field to distinguish them from given texts in the excel form for instance 'P-1.1-AuditComment'. |
||
- We logged in to EC2 and connect our RDS database that we use in WordPress on the command line. Created a sample table called wp-demo-table and give necessary columns that store our test data. |
- We logged in to EC2 and connect our RDS database that we use in WordPress on the command line. Created a sample table called wp-demo-table and give necessary columns that store our test data. |
||
| Line 169: | Line 169: | ||
- We are asked to create a log-in structure therefore we searched some bootstrap libraries and templates to make the visualization better. |
- We are asked to create a log-in structure therefore we searched some bootstrap libraries and templates to make the visualization better. |
||
- For the login page, we create a table on the database to store users and created PHP files for posts and get requests for users that we use like controllers on the APIs. |
- For the login page, we create a table on the database to store users and created PHP files for posts, and get requests for users that we use like controllers on the APIs. |
||
- We are trying to detect the user types like admin or regular user |
- We are trying to detect the user types like admin or regular user to give different privileges and use them to check if the user has permission to view or edit the form pages. |
||
'''Problems: ''' |
'''Problems: ''' |
||
| Line 192: | Line 192: | ||
---- |
---- |
||
'''Accomplishments: ''' |
'''Accomplishments: ''' |
||
- Able to integrate bootstrap to WordPress pages |
- Able to integrate bootstrap to WordPress pages to develop a responsive site. |
||
- Found a plug-in called Ultimate Member which provides us with user authentication like add, update, and delete, and gives different privileges according to the roles of users and specific authorization for each page or post. |
- Found a plug-in called Ultimate Member which provides us with user authentication like add, update, and delete, and gives different privileges according to the roles of users and specific authorization for each page or post. |
||
| Line 204: | Line 204: | ||
'''Problems: ''' |
'''Problems: ''' |
||
- Members/users page provided by the Ultimate Member plug-in |
- Members/users page provided by the Ultimate Member plug-in to list the current users and delete and update them cannot be opened. Gives an error like "s.ajax is not defined", which is a jquery code. Even if we get the script correctly for the site and use jquery somewhere else, we could not find any solution to that error yet. |
||
'''To-Do: ''' |
'''To-Do: ''' |
||
| Line 241: | Line 241: | ||
- We will be adding the new forms dynamically by using our functionality in the system. |
- We will be adding the new forms dynamically by using our functionality in the system. |
||
- We need to understand the relation between the fields and what we mean is that whenever the users, for example, check the 'C' column, we need to know which places or |
- We need to understand the relation between the fields and what we mean is that whenever the users, for example, check the 'C' column, we need to know which places or areas in the rows it affects. |
||
- We need to figure out how to make changes to the current users using created page by the plugin. |
- We need to figure out how to make changes to the current users using created page by the plugin. |
||
| Line 247: | Line 247: | ||
- We need to work on authorization by users' roles on the pages specifically. |
- We need to work on authorization by users' roles on the pages specifically. |
||
'''Week |
'''Week 9:''' |
||
'''Date''': 11/20/2022 |
'''Date''': 11/20/2022 |
||
| Line 268: | Line 268: | ||
- We will try to add all the forms to the application and display them at least in the forms list and with their default contents. |
- We will try to add all the forms to the application and display them at least in the forms list and with their default contents. |
||
- We need to understand the relation between the fields and what we mean is that whenever the users, for example, check the 'C' column, we need to know which places or |
- We need to understand the relation between the fields and what we mean is that whenever the users, for example, check the 'C' column, we need to know which places or areas in the rows it affects. |
||
'''Week 10:''' |
|||
'''Date''': 11/28/2022 |
|||
'''Attandence''': Ayberk Toptan, Aral Sen, Can Tufekci |
|||
---- |
|||
'''Accomplishments: ''' |
|||
- We added almost all forms to the application. |
|||
- We list the forms as dropdowns in the menu and once the user has one of them all the forms with the chosen type will be displayed in the table. |
|||
- We moved our codes to the AWS EC2 instance. We fixed the necessary configurations between the database and the application. |
|||
- Fixed the save button functionality to save the current data of the rows right after we add new rows or forms to the application. |
|||
'''Problems: ''' |
|||
- Even if we gave the correct connection string and properties, there was a problem executing SQL Queries. |
|||
'''To-Do: ''' |
|||
- We will try to fix the connection and SQL query execution problem. |
|||
- After we complete all the forms to add properly to the app, we have to focus on the relations between checkboxes like which one affects which row or where. |
|||
'''Week 11:''' |
|||
'''Date''': 12/04/2022 |
|||
'''Attandence''': Ayberk Toptan, Aral Sen, Can Tufekci |
|||
---- |
|||
'''Accomplishments: ''' |
|||
- Fixed some displaying issues on some forms. |
|||
- Fixed the SQL query execution problem that does not occur while working locally but occurs on AWS. |
|||
- Added the rest of the forms to the site and do some tests because sometimes saving functionality did not work on some forms. |
|||
- Put the next and back buttons properly and made them usable for every form on the site. |
|||
'''Problems: ''' |
|||
- We are using a plug-in but we have not been able to overcome the user authentication problems on AWS even though we do not have them locally. |
|||
'''To-Do: ''' |
|||
- We will try to fix the user authentication problem with the ultimate member plug-in on AWS. |
|||
- Once we fix it, we are thinking to be prepared for the presentation during finals week. |
|||
Latest revision as of 03:58, 5 December 2022
Week 1:
Date: 09/25/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- The project was started in a meeting with Professor Jones and Mr. Dutcher.
- Once we get our credentials for AWS Cloud Training, we started to work on that at first.
- In Cloud Guru, the first three chapters and almost half of chapter 4 were completed.
- We found a couple of tutorials about WordPress since we do not have any experience with it.
- We learned some fundamentals of WordPress by watching tutorials from FreeCodeCamp.
Problems:
- We could not connect to AWS Amazon Console via the given link in the email.
- Once we try to log in, the site is redirected to the change password page to continue to AWS Console after doing so. However, our accounts are not allowed to change passwords. We sent an email but we have not been able to get any response yet.
To-Do:
- Our second meeting was planned to be done on 09/28/2022 at 3.20 pm.
- Fix the login problem on AWS Console.
- Keep working on AWS Cloud training on Cloud Guru.
- After coming somewhere on the fundamentals of WordPress, try to practice them locally by opening an apache server as localhost. Then, learn how to integrate, and connect AWS and WordPress.
Week 2:
Date: 10/02/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- Completed weekly meetings with Professor Jones and Mr. Dutcher.
- After we got our credentials we kept working on AWS Cloud architecture on Cloud Guru.
- Searched and studied how to integrate and make WordPress Sites as working with AWS.
- Made a couple of examples that we saw in the tutorials on the architecture we created.
Problems:
- No problem occurred this week.
To-Do:
- We will be working on the tutorials on Cloud Guru for AWS Cloud architecture.
- We will be starting to develop the forms in the documents shared with us on the.
- Our main aim next week is to complete as many forms on the WordPress Site besides training the AWS.
Week 3:
Date: 10/10/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- Completed our weekly meeting with Professor Jones and Mr. Dutcher.
- We kept studying tutorials on AWS Cloud architecture on Cloud Guru.
- Created all necessary components like EC2, S3, and relational database RDS on AWS.
- Build the EC2 as Linux ubuntu operating system and connected it via ssh from our terminals.
- Downloaded necessary packages for WordPress and connected our WordPress Sites with the database that we created on AWS.
- Opened WordPress from the AWS EC2 server and made another post (page) in WordPress as a little demo.
Problems:
- Even if we did everything as same as in the tutorials, we were unable to create an EC2 server as an Amazon Linux instance.
- When we create the EC2 as Amazon Linux, we were not allowed to install the necessary packages for WordPress and even some simple terminal commands like "yum -y update".
To-Do:
- We will be working on the tutorials on Cloud Guru for AWS Cloud architecture.
- We will create a domain from AWS and try to launch our WordPress Sites on that domain.
- We will be starting to develop the decided form while thinking about how to develop it as user-friendly.
- We are aiming to complete at least one form tab, and make sure the fields are usable and possibly the crud operations can be done.
Week 4:
Date: 10/16/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- Completed our weekly meeting with Professor Jones and Mr. Dutcher.
- Worked on how to make form designs.
- Found and plugin and create three pages with data tables for forms.
- Added first three form pages of Pos Harvest Operations.
- Added necessary form input fields to the rows.
Problems:
- Could not figure out how to get entered data into the fields and put them into the database with the page id of the page that they belong
To-Do:
- We will be working on how to solve a problem that I mentioned above in the problems section.
- We will create more form pages once we can get data from form fields and can put them into the AWS RDS database.
Week 5:
Date: 10/23/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- Completed our weekly meeting with Mr. Dutcher.
- Worked on how to fix the problem that occurred the previous week.
- Found a couple of example solutions that can we use with the plug-in we use.
- Tried to implement and execute solutions that we found.
- We informed our problem to Mr. Dutcher and showed what we have tried and gotten as a result of our actions completed so far.
- Mr. Dutcher gave us a comment about using LAMP Stack integrated with AWS to perform data transactions outside of WordPress.
Problems:
- We got some errors and could be able to fix the problem that we had the previous week.
To-Do:
- We will be working on how to solve a problem that I mentioned above in the problems section.
- We will work on and learn LAMP Stack.
- We will try to create a solution to our problem using LAMP Stack.
Week 6:
Date: 10/31/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- Worked on putting HTML codes on WordPress pages to create form structure. Give unique IDs for every input field to distinguish them from given texts in the excel form for instance 'P-1.1-AuditComment'.
- We logged in to EC2 and connect our RDS database that we use in WordPress on the command line. Created a sample table called wp-demo-table and give necessary columns that store our test data.
- Made PHP files like create.php that gets post request from the site and separates the values according to column names. Creates SQL query and executes it to save data on the database. Finally, it returns the page the user enters input data.
- We created a file called read.php for demo and test to read requested data from the database and put the proper fields on the page site once the user directs that page or refreshes it or even after submitting entered data.
- We are asked to create a log-in structure therefore we searched some bootstrap libraries and templates to make the visualization better.
- For the login page, we create a table on the database to store users and created PHP files for posts, and get requests for users that we use like controllers on the APIs.
- We are trying to detect the user types like admin or regular user to give different privileges and use them to check if the user has permission to view or edit the form pages.
Problems:
- No problem has occurred yet.
To-Do:
- We will be finishing the log-in page.
- Storing users with their types and giving them different permissions.
- Once we finish the log-in page and code the permission checking for viewing and editing forms, we aim for users to open the chosen form according to their permissions.
Week 7:
Date: 11/06/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- Able to integrate bootstrap to WordPress pages to develop a responsive site.
- Found a plug-in called Ultimate Member which provides us with user authentication like add, update, and delete, and gives different privileges according to the roles of users and specific authorization for each page or post.
- Figured out how to use Ultimate Member and integrated it into our WordPress site, as a result now we have authentication and authorization on the website.
- Found a way to make the forms more user-defined like giving them chance to add rows so that the question needed to be answered can be defined by the user also. In this way, we do not have to make them hard-coded.
- Able to add new rows to the form, and put the rows needed input fields. Then figured out how to put that data into the database and get it by matching it with the page id and row id.
Problems:
- Members/users page provided by the Ultimate Member plug-in to list the current users and delete and update them cannot be opened. Gives an error like "s.ajax is not defined", which is a jquery code. Even if we get the script correctly for the site and use jquery somewhere else, we could not find any solution to that error yet.
To-Do:
- We will be looking for any solution for the error that we described above.
- We will be finishing crud operations for one form and then we will keep adding other forms by getting that finished form as an example.
- We will try to make an option for users to decide whether to start a new empty form or keep updating the form that they already started.
Week 8:
Date: 11/13/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- Fixed last week's problem which was displaying current users on the users' page automatically created by the authentication plugin on WordPress.
- Was able to make the form container responsive according to the width and height of the page that they currently are displayed.
- Made the forms dynamically which means that the admin users are now able to update forms by adding new rows by entering row numbers, the questions that will be answered or the input fields will be filled according to that, and MAN and DOC columns. Then the new rows will be added to the database according to the page number which means the form number that they belong and the page will be updated with the new data.
- Once the users are done with filling out the form when they click the save button at the end, the form data will be sent to the database and according to the page id and row id, the form data will be updated on the database.
- When the update operation is done, whenever the users open the page, the new values or data entered previously will be seen on the form.
- We accomplished these by coding the backend side, for instance, we wrote PHP pages that we use like API controllers to perform CRUD operations.
Problems:
- No problems have occurred for this week yet.
To-Do:
- We will be adding the new forms dynamically by using our functionality in the system.
- We need to understand the relation between the fields and what we mean is that whenever the users, for example, check the 'C' column, we need to know which places or areas in the rows it affects.
- We need to figure out how to make changes to the current users using created page by the plugin.
- We need to work on authorization by users' roles on the pages specifically.
Week 9:
Date: 11/20/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- We coded single pages for both forms where we listed them and the contents of the forms. We were able to make the functionality dynamically. What we mean by that is we are adding new forms and contents of the forms as an admin dynamically and as soon as new changes are added we show them on the proper page. For instance, if we add a new form it will be seen in the forms list and will be clickable. If we click it, the default contents of it will be shown and rows for that form can be added dynamically also.
- We are displaying the menu according to if the user logged in or not and what is user's role for privileges is.
- We figured out how to display all users and how to make changes on them by role privileges like deleting a user if the current user is admin.
Problems:
- No problems have occurred for this week yet.
To-Do:
- We will try to add all the forms to the application and display them at least in the forms list and with their default contents.
- We need to understand the relation between the fields and what we mean is that whenever the users, for example, check the 'C' column, we need to know which places or areas in the rows it affects.
Week 10:
Date: 11/28/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- We added almost all forms to the application.
- We list the forms as dropdowns in the menu and once the user has one of them all the forms with the chosen type will be displayed in the table.
- We moved our codes to the AWS EC2 instance. We fixed the necessary configurations between the database and the application.
- Fixed the save button functionality to save the current data of the rows right after we add new rows or forms to the application.
Problems:
- Even if we gave the correct connection string and properties, there was a problem executing SQL Queries.
To-Do:
- We will try to fix the connection and SQL query execution problem.
- After we complete all the forms to add properly to the app, we have to focus on the relations between checkboxes like which one affects which row or where.
Week 11:
Date: 12/04/2022
Attandence: Ayberk Toptan, Aral Sen, Can Tufekci
Accomplishments:
- Fixed some displaying issues on some forms.
- Fixed the SQL query execution problem that does not occur while working locally but occurs on AWS.
- Added the rest of the forms to the site and do some tests because sometimes saving functionality did not work on some forms.
- Put the next and back buttons properly and made them usable for every form on the site.
Problems:
- We are using a plug-in but we have not been able to overcome the user authentication problems on AWS even though we do not have them locally.
To-Do:
- We will try to fix the user authentication problem with the ultimate member plug-in on AWS.
- Once we fix it, we are thinking to be prepared for the presentation during finals week.