Open
Conversation
PLUGIN CORRUPT ONLY CHANGE PUBLIC.PHP IN SERVER FOR LOCAL MACHINE PLEASE UPLOAD OLD PLUGIN WITH ONLY MODIFICATE PUBLIC.PHP
Collaborator
|
Thank you for your work. Can you be more specific with your fix? I do not see any difference with your suggested changes and your changes are in the |
Author
|
When something was updated or modified, because we saw your signature in the modification and some ISPs updated with the new version 1.2, this error appears
Fatal error: Uncaught Error: Class "App\Argentinacae\WSAA" not found in /data/ucrm/data/plugins/argentina-afip-invoices/classes/Argentinacae/runcae.php:10 Stack trace: #0 /data/ucrm/data/plugins/argentina-afip-invoices/classes/Argentinacae/formatinvoice.php(324): runCae('0002', 'B', '06', Array, '30717035654', '1') #1 /data/ucrm/data/plugins/argentina-afip-invoices/public.php(76): formatInvoice('1', '0002', '9/01/2021', '1') #2 /usr/src/ucrm/web/_plugins/argentina-afip-invoices/public.php(3): require_once('/data/ucrm/data...') #3 {main} thrown in /data/ucrm/data/plugins/argentina-afip-invoices/classes/Argentinacae/runcae.php on line 10
We are currently sending ourselves the 1.1 file and modifying line 455 of client.php. we generated a post and we put you in the ubiquiti community
Diego
From: Jan Procházka ***@***.***>
Reply-To: Ubiquiti-App/UCRM-plugins ***@***.***>
Date: Friday, 12 May 2023, 02:45
To: Ubiquiti-App/UCRM-plugins ***@***.***>
Cc: Diego Roman ***@***.***>, Author ***@***.***>
Subject: Re: [Ubiquiti-App/UCRM-plugins] FIX OLD AFIP PLUG (PR #299)
Thank you for your work. Can you be more specific with your fix? I do not see any difference with your suggested changes and your changes are in the GuzzleHttp\Client.php file. Also, I am not able to test AFIP so the bug can happen. Thank you for your help.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PLUGIN CORRUPT ONLY CHANGE PUBLIC.PHP IN SERVER FOR LOCAL MACHINE
PLEASE UPLOAD OLD PLUGIN WITH ONLY MODIFICATE PUBLIC.PHP
To release a new version of a plugin, we suggest the following checklist. Checking these locally before pushing to the repository gives you immediate feedback, instead of waiting for the repository to automatically run the checks.
bash php-cs-check.shto check for valid PHP codeplugins/directory, runphp ../pack-plugin.php $YOUR_PLUGIN, where $YOUR_PLUGIN is the directory name of your plugin; this creates the installable packagecomposer.json, this will check it and install the dependencies - if this reports as "outdated", please fix by runningcomposer updatein your plugin's directoryphp validate.phpplugins.jsonis outdated, runphp generate-json.php > plugins.jsonto update it.