Description We need a more intuitive presentation for this boxes.

Step To Reproduce Steps to reproduce the behavior:

1. Go to 'Forms -> Create / Select A form'
2. Click on 'PDF '
3. Scroll down to 'PDF List'
4. See error

Expected behavior We can strip the borders and background so it would stand as a standard input box. Optional : Add a message like the system status.

Screenshots If applicable, add screenshots to help explain your problem.

Description

Issue: #915 Test all our UI components to ensure consistency when making changes.

Testing instructions

1. Start Docker. Note: if running Local By Flywheel, first run docker-machine start, then docker-machine env and run the command that gets spit out to configure your shell e.g eval $(docker-machine env).
2. Copy .env.example to .env and replace 0000000000000000 with a valid Elite license key in .env
3. Run ./bin/setup-local-env.sh from the command line
4. Run yarn run test:e2e / yarn run test:e2e:headless

Checklist:

• [x] I've tested the code.
• [x] My code is easy to read, follow, and understand
• [x] My code follows the accessibility standards.
• [x] My code has proper inline documentation / docblocks.

Hello to Australia from Czech republic, How can I exclude some element from pdf? When I put css "exclude", it works fine, but how exclude element without css possibility, like here: https://gravitywiz.com/documentation/gravity-forms-unique-id/ There is not possible css, so mayby put somthing to function.php?

Create a separate method that returns our errors and notices messages exclusively to Gravity PDF pages.

NOTE: This may need some improvements on how to properly initialize the Helper_Notice class exclusively to Gravity PDF pages as well.

Description

Testing instructions

Install Gravity Forms Akismet Add-On. Its default error message should not display on PDF settings.

Screenshots

Checklist:

• [x] I've tested the code.
• [ ] My code is easy to read, follow, and understand
• [ ] My code follows the accessibility standards.
• [ ] My code has proper inline documentation / docblocks.

Additional Comments

Enough people have asked, so it's worth giving users the option to show a summary table or all nested form fields.

Working sample:

// Gravity PDF Nested Forms Format
class Field_Form_Original extends \GFPDF\Helper\Fields\Field_Form {
    public function html( $value = '', $label = true ) {
        add_filter( 'gpnf_template_args', function( $args ) {
            $args['template'] = 'nested-entries-detail-simple';
            return $args;
        } );
        $html = GFCommon::get_lead_field_display( $this->field, $this->get_value(), $this->entry['currency'] );
        $html = apply_filters( 'gform_entry_field_value', $html, $this->field, $this->entry, $this->form );
        return \GFPDF\Helper\Helper_Abstract_Fields::html($html);
    }
}
add_filter( 'gfpdf_field_class_form', function( $class, $field, $entry ) {
    return new Field_Form_Original( $field, $entry, GPDFAPI::get_form_class(), GPDFAPI::get_misc_class() );
}, 10, 3 );

GF_Field::get_value_entry_detail was called <strong>incorrectly</strong>. Override this method to handle array values Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 2.0.) in /srv/www/wordpress-default/wp- includes/functions.php on line 4091

Description

Previously, the generate function of Helper_Field_Container was not doing anything with the return value of process_skipped_fields. This causes field types which should not have a field container wrapped around them to have one wrapped around them.

This patch checks the return value of process_skipped_fields and stops generation if true. This will not leave the previous container open, because process_skipped_fields closes it if a skipped field is hit.

Testing instructions

1. Add a field type to the skip_fields array via the gfpdf_container_skip_fields filter, enable a display of a skipped field type (such as HTML) via the settings, or create a class for a field type such as page.
2. Observe that the field container HTML is no longer erroneously being generated.

Checklist:

• [x] I've tested the code.
• [x] My code is easy to read, follow, and understand
• [x] My code follows the accessibility standards.
• [x] My code has proper inline documentation / docblocks.

Description

WIP

Resolves #960

Testing instructions

Screenshots

Checklist:

• [ ] I've tested the code.
• [ ] My code is easy to read, follow, and understand
• [ ] My code follows the accessibility standards.
• [ ] My code has proper inline documentation / docblocks.

Additional Comments

Description

Issue: #1208

RTL languages like Arabic and Hebrew put WordPress admin in RTL mode, where everything is reversed. All functionality should work as expected under WP RTL mode.

Testing instructions

Screenshots

Checklist:

• [x] I've tested the code.
• [x] My code is easy to read, follow, and understand
• [ ] My code follows the accessibility standards.
• [x] My code has proper inline documentation / docblocks.

Additional Comments

Description WordPress will check PHP ~and WP versions~ and prevent an upgrade to a release that isn't compatible (https://core.trac.wordpress.org/ticket/43987). We should consider extending this behaviour to check the Gravity Forms version so that users don't upgrade to v6 and then have to downgrade right away if they aren't ready to upgrade to 2.5.

On the other hand, upgrading to 6.0 and then getting an error about an outdated version of Gravity Forms would encourage users to upgrade Gravity Forms as well, which would encourage users to keep up to date.

Description Gravity Forms has moved all their add-on uninstaller under Settings -> Uninstall. We should do the same

Step To Reproduce Steps to reproduce the behavior:

1. Go to Settings -> Uninstall with a Gravity Forms add-on enabled

Expected behavior Show Gravity PDF on this list

Screenshots

Description Currently, the Core Font Installer notice is shown on all WordPress admin pages outside of Gravity Forms, and any Gravity PDF pages. To reduce notice fatigue for users, only display the notice on the WordPress Plugin screen, all Gravity PDF pages, and the following Gravity Forms screens:

1. Form List
2. Form Settings
3. Form Entry List
4. Form Entry Details

Screenshots

Description

Add PHP 8.2 test runner for PHPUnit

Testing instructions

Screenshots

Checklist:

• [ ] I've tested the code.
• [ ] My code is easy to read, follow, and understand
• [ ] My code follows the accessibility standards.
• [ ] My code has proper inline documentation / docblocks.

Additional Comments

Description

Deactivating a license that has already been deactivated via other means will produce an invalid UI state.

Step To Reproduce Steps to reproduce the behavior:

1. Activate a License Key for a Gravity PDF extension at Forms -> Settings -> PDF -> License
2. Go to GravityPDF.com/account/, locate the license key under Licenses, and then deactivate your site
3. Back in WordPress, click the "Deactivate License" button, and you'll get an error about the license not being activated on the site

Expected behavior

At step 3, we should delete the license key from the database and now show the Deactivate License button any longer. The UI should be ready to accept a fresh license key to activate the plugin again.

Screenshots

Description Gravity Forms payment add-ons like Stripe offer a Free Trial Subscription. When this is enabled, the Product Table generated by Gravity Forms will include a line item called "Free Trial" with a $0.00 value and in the subtotal area will include the text "Trial Discount" which zeros out the product total.

Gravity PDF doesn't currently support this feature when generating the Product Table or premium invoices.

Step To Reproduce Steps to reproduce the behavior:

1. Install Stripe
2. Configure Stripe in Test Mode
3. Create a form with a product
4. Set up a Stripe Feed with a subscription and free trial enabled
5. Submit the form
6. View the Product table on the Entry Details page and/or Notification email
7. Set up a Core PDF on the form and view the PDF

Expected behavior The Product table generated by Gravity PDF for Core and Universal templates should include the free trial information.

Support for this feature should be added to premium Invoice PDFs as well.

Description

The Noto Sans Bold TTF font file (downloaded direct from fonts.google.com) causes a PHP fatal error due to a max memory issue upon adding to the Font Manager.

The reasons for the fatal error is when mPDF is parsing the font file the OTL Ligature set data extracted from the file is creating some very large loops. This suggests there is an underlying issue with mPDF's font reader, but I don't know enough about working with binary font files in PHP, or their structure, to make any sort of determination.

The workaround I have come up with is to disable the OTL checker if the installation fails and the user selects retry. This will prevent the Ligature set from being extracted from the OTL font data, and stop the fatal error.

Step To Reproduce Steps to reproduce the behavior:

1. Download the Noto Sans zip from Google Fonts
2. Open the Font Manager
3. In the Add Font panel, select the Noto Sans Bold TTF font file for the Regular box and save
4. See error

Expected behavior The font successfully saves.

Description Gravity Flow registered a number of fields for Gravity Forms. While the fallback Gravity PDF uses will correctly display these in the PDFs, some are not optimized in the $form_data array.

Let's register specific PDF fields for these Gravity Flow fields and determine the best output and the best $form_data array structure.