Merge pull request #12 from cp-psource/MP-PDF-RECHNUNG

Mp pdf rechnung
cp-psource · Nov 26, 2023 · 48b9004 · 48b9004
2 parents c319478 + 76c4605
commit 48b9004
Show file tree

Hide file tree

Showing 164 changed files with 60,271 additions and 60,265 deletions.
diff --git a/.github/workflows/node.js.yml b/.github/workflows/node.js.yml
@@ -1,31 +1,31 @@
-# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
-# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs
-
-name: Node.js CI
-
-on:
-  push:
-    branches: [ "master" ]
-  pull_request:
-    branches: [ "master" ]
-
-jobs:
-  build:
-
-    runs-on: ubuntu-latest
-
-    strategy:
-      matrix:
-        node-version: [14.x, 16.x, 18.x]
-        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
-
-    steps:
-    - uses: actions/checkout@v3
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v3
-      with:
-        node-version: ${{ matrix.node-version }}
-        cache: 'npm'
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs
+
+name: Node.js CI
+
+on:
+  push:
+    branches: [ "master" ]
+  pull_request:
+    branches: [ "master" ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [14.x, 16.x, 18.x]
+        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
+
+    steps:
+    - uses: actions/checkout@v3
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v3
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
+    - run: npm ci
+    - run: npm run build --if-present
+    - run: npm test
diff --git a/README.md b/README.md
diff --git a/includes/addons/mp-pdf-invoice/class-mp-pdf-invoice-addon.php b/includes/addons/mp-pdf-invoice/class-mp-pdf-invoice-addon.php
@@ -1,9 +1,8 @@
 <?php
 
-/**
- * @author: Hoang Ngo
- */
-require_once dirname( __FILE__ ) . '/class-mp-pdf-invoice.php';
+namespace MP_PDF_Invoice_Addon;
+
+use MP_PDF_Invoice_Addon\MP_PDF_Invoice;
 
 class MP_PDF_Invoice_Addon {
 

diff --git a/includes/addons/mp-pdf-invoice/class-mp-pdf-invoice.php b/includes/addons/mp-pdf-invoice/class-mp-pdf-invoice.php
@@ -1,9 +1,14 @@
 <?php
 
-/**
- * @author: Hoang Ngo
- *12.3.20 alles fein DN
- */
+namespace MP_PDF_Invoice_Addon;
+
+use Dompdf\Dompdf;
+
+$dompdf = new Dompdf();
+$options = $dompdf->getOptions();
+$options->setDefaultFont('Courier');
+$dompdf->setOptions($options);
+
 class MP_PDF_Invoice {
 
 	const PDF_INVOICE = 'invoice', PDF_SLIP = 'slip';
@@ -16,7 +21,7 @@ class MP_PDF_Invoice {
 	 */
 	public function __construct() {
 		if ( ! class_exists( 'DOMPDF' ) ) {
-			require_once dirname( __FILE__ ) . '/vendors/dompdf/dompdf_config.inc.php';
+			require_once dirname( __FILE__ ) . '/vendors/dompdf/autoload.inc.php';
 		}
 		$this->settings = mp_get_setting( 'pdf_invoice' );
 	}

diff --git a/includes/addons/mp-pdf-invoice/vendors/dompdf/CONTRIBUTING.md b/includes/addons/mp-pdf-invoice/vendors/dompdf/CONTRIBUTING.md
@@ -1,76 +1,76 @@
-# How to contribute
-
-- [Getting help](#getting-help)
-- [Submitting bug reports](#submitting-bug-reports)
-- [Contributing code](#contributing-code)
-
-## Getting help
-
-Community discussion, questions, and informal bug reporting is done on the
-[dompdf Google group](http://groups.google.com/group/dompdf). You may also 
-seek help on
-[StackOverflow](http://stackoverflow.com/questions/tagged/dompdf).
-
-## Submitting bug reports
-
-The preferred way to report bugs is to use the
-[GitHub issue tracker](http://github.com/dompdf/dompdf/issues). Before 
-reporting a bug, read these pointers.
-
-**Please search inside the bug tracker to see if the bug you found is not already reported.**
-
-**Note:** The issue tracker is for *bugs* and *feature requests*, not requests for help.
-Questions should be asked on the
-[dompdf Google group](http://groups.google.com/group/dompdf) instead.
-
-### Reporting bugs effectively
-
-- dompdf is maintained by volunteers. They don't owe you anything, so be
-  polite. Reports with an indignant or belligerent tone tend to be moved to the
-  bottom of the pile.
-
-- Include information about **the PHP version on which the problem occurred**. Even
-  if you tested several PHP version on different servers, and the problem occurred
-  in all of them, mention this fact in the bug report.
-  Also include the operating system it's installed on. PHP configuration can also help,
-  and server error logs (like Apache logs)
-
-- Mention which release of dompdf you're using (the zip, the master branch, etc).
-  Preferably, try also with the current development snapshot, to ensure the
-  problem has not already been fixed.
-
-- Mention very precisely what went wrong. "X is broken" is not a good bug
-  report. What did you expect to happen? What happened instead? Describe the
-  exact steps a maintainer has to take to make the problem occur. We can not
-  fix something that we can not observe.
-
-- If the problem can not be reproduced in any of the demos included in the
-  dompdf distribution, please provide an HTML document that demonstrates
-  the problem. There are a few options to show us your code:
-   - [JS Fiddle](http://jsfiddle.net/)
-   - [dompdf debug helper](http://eclecticgeek.com/dompdf/debug.php) (provided by @bsweeney)
-   - Include the HTML/CSS inside the bug report, with
-   [code highlighting](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#wiki-code).
-
-## Contributing code
-
-- Make sure you have a [GitHub Account](https://github.com/signup/free)
-- Fork [dompdf](https://github.com/dompdf/dompdf/)
-  ([how to fork a repo](https://help.github.com/articles/fork-a-repo))
-- *Make your changes on the dev branch* or the most appropriate feature branch. Please only patch 
-  the master branch if you are attempting to address an urgent bug in the released code.
-- Add a simple test file in `www/test/`, with a comprehensive name.
-- Submit a pull request
-([how to create a pull request](https://help.github.com/articles/fork-a-repo))
-
-### Coding standards
-
-- 2 spaces per indentation level, no tabs.
-- spaces inside `if` like this:
-```php
-if ( $foo == "bar" ) {
-  //
-}
-```
-- booleans in lowercase
-- opening braces *always* on the same line
+# How to contribute
+
+- [Getting help](#getting-help)
+- [Submitting bug reports](#submitting-bug-reports)
+- [Contributing code](#contributing-code)
+
+## Getting help
+
+Community discussion, questions, and informal bug reporting is done on the
+[dompdf Google group](http://groups.google.com/group/dompdf). You may also 
+seek help on
+[StackOverflow](http://stackoverflow.com/questions/tagged/dompdf).
+
+## Submitting bug reports
+
+The preferred way to report bugs is to use the
+[GitHub issue tracker](http://github.com/dompdf/dompdf/issues). Before 
+reporting a bug, read these pointers.
+
+**Please search inside the bug tracker to see if the bug you found is not already reported.**
+
+**Note:** The issue tracker is for *bugs* and *feature requests*, not requests for help.
+Questions should be asked on the
+[dompdf Google group](http://groups.google.com/group/dompdf) instead.
+
+### Reporting bugs effectively
+
+- dompdf is maintained by volunteers. They don't owe you anything, so be
+  polite. Reports with an indignant or belligerent tone tend to be moved to the
+  bottom of the pile.
+
+- Include information about **the PHP version on which the problem occurred**. Even
+  if you tested several PHP version on different servers, and the problem occurred
+  in all of them, mention this fact in the bug report.
+  Also include the operating system it's installed on. PHP configuration can also help,
+  and server error logs (like Apache logs)
+
+- Mention which release of dompdf you're using (the zip, the master branch, etc).
+  Preferably, try also with the current development snapshot, to ensure the
+  problem has not already been fixed.
+
+- Mention very precisely what went wrong. "X is broken" is not a good bug
+  report. What did you expect to happen? What happened instead? Describe the
+  exact steps a maintainer has to take to make the problem occur. We can not
+  fix something that we can not observe.
+
+- If the problem can not be reproduced in any of the demos included in the
+  dompdf distribution, please provide an HTML document that demonstrates
+  the problem. There are a few options to show us your code:
+   - [JS Fiddle](http://jsfiddle.net/)
+   - [dompdf debug helper](http://eclecticgeek.com/dompdf/debug.php) (provided by @bsweeney)
+   - Include the HTML/CSS inside the bug report, with
+   [code highlighting](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#wiki-code).
+
+## Contributing code
+
+- Make sure you have a [GitHub Account](https://github.com/signup/free)
+- Fork [dompdf](https://github.com/dompdf/dompdf/)
+  ([how to fork a repo](https://help.github.com/articles/fork-a-repo))
+- *Make your changes on the dev branch* or the most appropriate feature branch. Please only patch 
+  the master branch if you are attempting to address an urgent bug in the released code.
+- Add a simple test file in `www/test/`, with a comprehensive name.
+- Submit a pull request
+([how to create a pull request](https://help.github.com/articles/fork-a-repo))
+
+### Coding standards
+
+- 2 spaces per indentation level, no tabs.
+- spaces inside `if` like this:
+```php
+if ( $foo == "bar" ) {
+  //
+}
+```
+- booleans in lowercase
+- opening braces *always* on the same line