Draft:Specification Module Public Portal - Revision history

Eldy: /* Some requirements */

2023-08-21T01:01:11Z

Some requirements

← Older revision		Revision as of 01:01, 21 August 2023
Line 6:		Line 6:
	= Some requirements =		= Some requirements =
	* Must be a Dolibarr module called "WebPortal"		* Must be a Dolibarr module called "WebPortal"
			* Only 1 permission will be used : "Administer users of the customer/partner webportal module"
	* The portal must be pages hosted into /public/webportal/		* The portal must be pages hosted into /public/webportal/
	* Code must follow dolibarr development rules (https://wiki.dolibarr.org/index.php?title=Language_and_development_rules)		* Code must follow dolibarr development rules (https://wiki.dolibarr.org/index.php?title=Language_and_development_rules)

2023-08-16T12:43:36Z

← Older revision		Revision as of 12:43, 16 August 2023
Line 17:		Line 17:
	* login from website for users of a website. The column site contains "dolibarr_website" and we store the id of website into fk_website		* login from website for users of a website. The column site contains "dolibarr_website" and we store the id of website into fk_website
	So we will also use it to store login for the external portal access too:		So we will also use it to store login for the external portal access too:
	* the column "site" will contains "dolibarr_portal" and fk_soc will contains the id of the thirdparty. This column must appears into the form "Type of website" with possible "Web site (CMS Dolibarr)" if module website dolibarr is on, "Native ~~customer~~ portal" (if module webportal is on), ...		* the column "site" will contains "dolibarr_portal" and fk_soc will contains the id of the thirdparty. This column must appears into the form "Type of website" with possible "Web site (CMS Dolibarr)" if module website dolibarr is on, "Native Dolibarr portal" (if module webportal is on), ...

2023-08-16T12:42:24Z

← Older revision		Revision as of 12:42, 16 August 2023
Line 17:		Line 17:
	* login from website for users of a website. The column site contains "dolibarr_website" and we store the id of website into fk_website		* login from website for users of a website. The column site contains "dolibarr_website" and we store the id of website into fk_website
	So we will also use it to store login for the external portal access too:		So we will also use it to store login for the external portal access too:
	* the column "site" will contains "dolibarr_portal" and fk_soc will contains the id of the thirdparty		* the column "site" will contains "dolibarr_portal" and fk_soc will contains the id of the thirdparty. This column must appears into the form "Type of website" with possible "Web site (CMS Dolibarr)" if module website dolibarr is on, "Native customer portal" (if module webportal is on), ...


	On the record of a thirdparty, enabling the [[Module Public Portal]] must enable the new tab will be visible to show all accounts/login (=record of table llx_societe_account) linked to this thirdparty.		On the record of a thirdparty, enabling the [[Module Public Portal]] must enable the new tab will be visible to show all accounts/login (=record of table llx_societe_account) linked to this thirdparty.

2023-04-19T21:05:12Z

← Older revision		Revision as of 21:05, 19 April 2023
Line 11:		Line 11:

	= Login =		= Login =
	A table, called llx_societe_account, already exists to store login/pass for external ~~portalsor~~ external websites.		A table, called llx_societe_account, already exists to store login/pass for external portals or external websites.

	It is already used to store :		It is already used to store :
Line 19:		Line 19:
	* the column "site" will contains "dolibarr_portal" and fk_soc will contains the id of the thirdparty		* the column "site" will contains "dolibarr_portal" and fk_soc will contains the id of the thirdparty

	On the record of a thirdparty, enabling the ~~module~~ Public ~~portal~~ must enable the new tab will be visible to show all accounts/login (=record of table llx_societe_account) linked to this thirdparty.		On the record of a thirdparty, enabling the [[Module Public Portal]] must enable the new tab will be visible to show all accounts/login (=record of table llx_societe_account) linked to this thirdparty.

	Note: This tab already exists but is enabled only when WEBSITE_USE_WEBSITE_ACCOUNTS is on.		Note: This tab already exists but is enabled only when WEBSITE_USE_WEBSITE_ACCOUNTS is on.

2023-04-19T21:02:28Z

← Older revision		Revision as of 21:02, 19 April 2023
Line 19:		Line 19:
	* the column "site" will contains "dolibarr_portal" and fk_soc will contains the id of the thirdparty		* the column "site" will contains "dolibarr_portal" and fk_soc will contains the id of the thirdparty

	On the record of a thirdparty, the module Public portal must enable the new tab will be visible to show all accounts/login (=record of table llx_societe_account) linked to this thirdparty.		On the record of a thirdparty, enabling the module Public portal must enable the new tab will be visible to show all accounts/login (=record of table llx_societe_account) linked to this thirdparty.

	Note: This tab already exists but is enabled only when WEBSITE_USE_WEBSITE_ACCOUNTS is on.		Note: This tab already exists but is enabled only when WEBSITE_USE_WEBSITE_ACCOUNTS is on.

2023-04-19T21:01:36Z

← Older revision		Revision as of 21:01, 19 April 2023
Line 11:		Line 11:

	= Login =		= Login =
	A table already exists to store login/pass for external ~~portals~~.		A table, called llx_societe_account, already exists to store login/pass for external portalsor external websites.

	It is already used to store :		It is already used to store :
	* login from external website (for example stripe customer key of a thirdparty). The column site contains "stripe".		* login from external website (for example stripe customer key of a thirdparty). The column site contains "stripe".

2023-04-13T10:03:40Z

← Older revision		Revision as of 10:03, 13 April 2023
Line 7:		Line 7:
	* Must be a Dolibarr module called "WebPortal"		* Must be a Dolibarr module called "WebPortal"
	* The portal must be pages hosted into /public/webportal/		* The portal must be pages hosted into /public/webportal/
	* Code must follow dolibarr development rules		* Code must follow dolibarr development rules (https://wiki.dolibarr.org/index.php?title=Language_and_development_rules)
	* Code for page list or crud classes must follow templates available into modulebuilder directory.		* Code for page list or crud classes must follow templates available into modulebuilder directory.

2023-04-13T06:41:53Z

Some requirements

← Older revision		Revision as of 06:41, 13 April 2023
Line 7:		Line 7:
	* Must be a Dolibarr module called "WebPortal"		* Must be a Dolibarr module called "WebPortal"
	* The portal must be pages hosted into /public/webportal/		* The portal must be pages hosted into /public/webportal/
			* Code must follow dolibarr development rules
			* Code for page list or crud classes must follow templates available into modulebuilder directory.

	= Login =		= Login =

2023-02-07T11:47:02Z

The portal page

← Older revision		Revision as of 11:47, 7 February 2023
Line 44:		Line 44:
	* A tab/menu with list of orders		* A tab/menu with list of orders
	* A tab/menu with list of invoices		* A tab/menu with list of invoices
			* No dependency on external javascript libraries (except the jquery already present into Dolibarr)

2023-02-07T11:44:56Z

The portal page

← Older revision		Revision as of 11:44, 7 February 2023
Line 37:		Line 37:
	The portal web site must contains:		The portal web site must contains:
	* A top banner similar to other public pages		* A top banner similar to other public pages
	* Must be able to surcharge the CSS		* Must be able to surcharge the CSS by adding CSS in a textarea
	* A home page		* A home page
	* A tab/menu with membership data in read or edit mode (if option was set)		* A tab/menu with membership data in read or edit mode (if option was set)