Most Common Errors

[DisposableHero]

Here you will find most common errors you will encounter during install/update/usage.

 

500 | Server Error

 

This really means nothing and it is not helpful at all. So please do not message me or open a forum topic with just this message (or a screenshot showing that blank page).

To understand what is going on we need more info about that error, what you can do;

 

• Enable APP_DEBUG in your env.php (by default it is disabled/false) and re-visit that page. There you will see the error in detail, you can post a full screenshot of that page.
• Check your laravel logs (they are located at storage\logs folder of your phpvms), the error would be recorded there will full details. Either you can send your full log, or just the part where the error is first recorded and afterwards.

 

Without proper details, no one can help you. So in short, you need to help me (or us) to get help back.   

 

Call to undefined function Dispo_... 

 

• You did not cleaned your app cache after installing/updating an addon
• One of your Disposable addons is out of date
• Your installation was not correct thus the function was not loaded
• You updated your modules, but one of your blades (pages) still trying to use a deprecated/deleted/non existing fuction (rare but can happen)

 

Widget ... was not found

 

• You did not cleaned your app cache after installing/updating an addon
• Your addon is out of date but you are trying to use a recent version's widget
• Your installation was not correct thus the widget was not loaded
• You are making a typo mistake
• You updated your modules, but one of your blades (pages) still trying to use a deprecated/deleted/non existing widget (rare but can happen)

 

Route not found ...

 

• You did not cleaned your app cache after installing/updating an addon
• Your addon is out of date but you are trying to use a recent version's route
• Your installation was not correct thus the route is not loaded
• You are making a typo mistake
• You updated your modules, but one of your blades (pages) still trying to use a deprecated/deleted/non existing route (rare but can happen)

 

Not a valid Alpha2 key ...

 

• Use ISO 2 letter country codes for airports you have (this is phpvms v7 standard)
• Do not use country names while manually entering airports, instead use 2 letter codes or better use the built-in lookup function of phpvms v7
• Do not import non phpvms v7 compatible data from 3rd party sources
• Do not expect me to not follow phpvms v7 standards and make modules work under every condition.

 

"Trying to get property ... of non-object" or "Attempt to read property ... on null"

 

Well, this literally means "I am trying to read ... from something, but that something does not exists". To better understand this, you need to check which line the error comes from, it may be many things but in theory the main referenced object is not there at all.

Imagine you are getting this error `Trying to get property 'name' of non-object` and it refers to line 86 of a blade, check that line to see where ->name is used and identify the main object.

 

<span class="badge badge-sm badge-info">{{ $airline->name }}</span>

$airline <== This is the main object
->name   <== This is the property

 

So now the error makes much sense like "I am trying to read the name of an airline, but the airline is not there at all"

 

When this happens ? It may happen when you delete something referenced by phpvms and considered as mandatory (thus no failsafe solution is defined) like a user  Once a user sends a pirep, that user's id is used in that pirep and gets referenced in many areas. Same happens to an airport and a fare too, once a pirep is sent using that airport/fare, it's id is now referenced in that pirep. So if you delete that user and/or airport or whatever it was for some reason, than this error may pop-up in many different places (when code tries to read some details about the reference)

 

Long story short, do not delete things if they are used/linked in somewhere else (mainly in pireps and finances) deactivate them instead. If you really need to delete them then you may need to handle all references to that object too. Either by adding failsafe solutions to each location they are being read or you need to delete the referencing object too (which may cause another and maybe bigger problems).

 

Better before deleting things, think twice or more and ask for support if you are not sure what will happen after deletion.

 

Can't DROP INDEX disposable_tech_id_index; check that it exists

 

This is something I can not re-create and provide an automated solution, but some users reported having this (2 or 3 until today) while installing Disposable Basic module. So here is what you need to do;

 

• Open your database workbench (phpmyadmin or similar)
• Navigate to `disposable_tech` table and drop all indexes of that table manually
• Then rename `disposable_tech` table to `disposable_tech_details`
• Add indexes back ( id => Unique, id => Primary, icao => Unique )
• Try visiting /update or admin > dashboard page again, migration should not fail now and module installation/update should be completed.

 

Object of class App\Support\Units\... could not be converted to int

 

This error is specific to development builds of phpvms released after 14 March 22 (Laravel9 update). Happens only if your duplicated blade is not properly updated by you and/or your theme developer.

Check the default blade offered by Disposable addon carefully, either use it by deleting/renaming your duplicate or apply the required changes to your duplicate.

 

Edited January 28, 2023 by DisposableHero
Added another common error