• Take time to read Forum Rules | Hot Note | Why You Choose Us?
  • We appreciate everyone who shares their resources and those who send them to us to be shared on our forum.

    We try as much as possible to share untouched or original script without nulling them. But incase you need a null version contact us and our nulling team will advise.

  • Submit ten (10) resources and apply to become a Moderator of Scriptzhub. | We are currently we are currently experiencing technical difficulties with email service. To create an account send your username and password to daviruzsystems@gmail.com.
Zaiproty - Agreement/Document signing Addon

Zaiproty - Agreement/Document signing Addon v1.1

No permission to download

Avinash

Administrator
Staff member
Avinash submitted a new resource:

Zaiproty - Agreement/Document signing Addon - The game-changing digital agreement addon for ZAIPROTY simplifies the tenant-owner relationship.

Zaiproty - Agreement/Document signing Addon. - CodeCanyon Item for Sale


The game-changing digital agreement addon for ZAIPROTY simplifies the tenant-owner relationship. With Zaiproty – Agreement/Document signing Addon, landlords can effortlessly create and sign agreements with...

Read more about this resource...
 
Hello,

Hope somebody can help me. I install the core Zaiproty 3.3 app and it works well. But if I install any of the addons using the standard admin menu option on the panel the installation fails. Did anyone manage to install the addons with the core systems? Any help will be appreciated.

Dana
 
to add more contect the addon installation controller call an API to the developers website but it will not return the expected answer. That may be the problem.
 
appologies for the burst of reply's but just want to add as much contect as possible. The attached picture show the api call used during the install of an addon
 

Attachments

  • addoncontroller.png
    addoncontroller.png
    393.7 KB · Views: 10
Awesome thank your support is great!

I updated a small syntax error in the Http::acceptJson() method call. It seems like the arrow (->) is encoded as ->. that gives an error so I use the arrow syntax directly:

$apiResponse = Http::acceptJson()->post('https://support.zainikthemes.com/api/745fca97c52e41daa70a99407edf44dd/glv', [
'app' => $code,
'is_localhost' => env('IS_LOCAL', false),
'app_build_version' => getCustomerCurrentBuildVersion(),
'addon_build_version' => getCustomerAddonBuildVersion($code),
]);

I get the attached error when I try to install the addon from the admin panel

Any suggestions?

Thanking you in advance
 

Attachments

  • error.png
    error.png
    52.7 KB · Views: 9
Dear Avinash,

I tested the code a bit more today and made some changes required by the Laravel syntax. Acopy of the revised code is below in this message. I now managed to get the code to work but get stuck when trying to select the option to install the addon. Refer to the short attached video of the error.

The point in the code for this error is on line 214:

214 throw new Exception('Something went wrong. Please try again');
215 break;

With the message
Something went wrong. Please try again

I am still learning the language and cannot resolve this. Please can you kindly assist me with this I will really appreciate it!

Updated controller code:

public function addonSaasFileStore(Request $request)
{
$request->validate([
'update_file' => 'bail|required|mimes:zip'
]);
set_time_limit(1200);
$path = storage_path('app/addons/' . $request->code . '.zip');
if (file_exists($path)) {
File::delete($path);
}
try {
$request->update_file->storeAs('addons/', $request->code . '.zip');
} catch (Exception $e) {
return $this->error([], $e->getMessage());
}
}
public function addonSaasFileExecute(Request $request)
{
if ($request->licenseStatus == 1) {
$request->validate([
'email' => 'required',
'purchase_code' => 'required'
]);
}
$purchase_code = $request->purchase_code;
$code = $request->code;
try {
$returnResponse = $this->addonSaasFileExecuteUpdate($code, $purchase_code, $request->email, $request->fullUrl());
if ($returnResponse['success'] == true) {
Auth::logout();
return $this->success([], __('Addon Installed Successfully'));
}
return $this->error([], json_encode($returnResponse['message']));
} catch (Exception $e) {
return $this->error([], $e->getMessage());
}
}
 

Attachments

  • zaiproty.zip
    423.4 KB · Views: 4
Dear Avinash,

I tested the code a bit more today and made some changes required by the Laravel syntax. Acopy of the revised code is below in this message. I now managed to get the code to work but get stuck when trying to select the option to install the addon. Refer to the short attached video of the error.

The point in the code for this error is on line 214:

214 throw new Exception('Something went wrong. Please try again');
215 break;

With the message
Something went wrong. Please try again

I am still learning the language and cannot resolve this. Please can you kindly assist me with this I will really appreciate it!

Updated controller code:

public function addonSaasFileStore(Request $request)
{
$request->validate([
'update_file' => 'bail|required|mimes:zip'
]);
set_time_limit(1200);
$path = storage_path('app/addons/' . $request->code . '.zip');
if (file_exists($path)) {
File::delete($path);
}
try {
$request->update_file->storeAs('addons/', $request->code . '.zip');
} catch (Exception $e) {
return $this->error([], $e->getMessage());
}
}
public function addonSaasFileExecute(Request $request)
{
if ($request->licenseStatus == 1) {
$request->validate([
'email' => 'required',
'purchase_code' => 'required'
]);
}
$purchase_code = $request->purchase_code;
$code = $request->code;
try {
$returnResponse = $this->addonSaasFileExecuteUpdate($code, $purchase_code, $request->email, $request->fullUrl());
if ($returnResponse['success'] == true) {
Auth::logout();
return $this->success([], __('Addon Installed Successfully'));
}
return $this->error([], json_encode($returnResponse['message']));
} catch (Exception $e) {
return $this->error([], $e->getMessage());
}
}
Everything is much simpler and applies to all existing modules.
1) unpack from the downloaded archive to the root of the site according to the directory hierarchy.
2) look in the archive in the config folder and open the file (config\agreement.php)
3) go to the database and open the setting table
4) take from file 2 ($app_code = PROTYAGREEMENT $build_version= 2 $current_version = 1.1)
And insert the following data
options_key => PROTYAGREEMENT_build_version
options_value => $build_version

options_key => PROTYAGREEMENT_current_version
options_value => $current_version

We reboot and everything works.... We do the same with the other modules....
File app\Http\Controllers\AddonUpdateController.php
You can restore it; we don’t need it and it doesn’t interfere....
 
Everything is much simpler and applies to all existing modules.
1) unpack from the downloaded archive to the root of the site according to the directory hierarchy.
2) look in the archive in the config folder and open the file (config\agreement.php)
3) go to the database and open the setting table
4) take from file 2 ($app_code = PROTYAGREEMENT $build_version= 2 $current_version = 1.1)
And insert the following data
options_key => PROTYAGREEMENT_build_version
options_value => $build_version

options_key => PROTYAGREEMENT_current_version
options_value => $current_version

We reboot and everything works.... We do the same with the other modules....
File app\Http\Controllers\AddonUpdateController.php
You can restore it; we don’t need it and it doesn’t interfere....
But we can unpack it even more simply from the previous answer, as I wrote further
in app\Http\Middleware\SaasModuleMiddleware.php
We present it as in the screenshot and everything works the same way for us. Only version checking is disabled when loading.... choose which one is better for yourself
 

Attachments

  • Screenshot 2023-12-28 132836.png
    Screenshot 2023-12-28 132836.png
    77.3 KB · Views: 3
Back
Top