Cannot check assets out to users after updating to 4.7.2 #7092
Comments
|
I can confirm this as well, just went to check out an asset and the user/asset/location fields show no results. |
|
I use CentOS 7 php version 7.1.30 on Apache |
|
Same problem for me |
|
The demo is running 4.7.0, and isn't displaying this issue, so something obviously between this release window. |
|
Same issue, when you try to search for a user on the checkout screen it shows the error "The Results could not be loaded". Using PHP 7.2.7 |
|
I also have the same issue. |
|
Same issue here |
|
Oddly creating new users allows you to check an asset out to them. . . @snipe hope you can shed some insight into this. |
That's not true though. The only thing that changed between 4.7.0 and 4.7.2 is the docker file and the version file: v4.7.0...master Can anyone give me app logs errors? I can't do anything without that. |
|
(Also make sure you've cleared all of your app view/route/etc caches, run migrations, etc) |
Where can I pull these logs for you? |
|
https://snipe-it.readme.io/docs/getting-help#section-step-3-check-your-app-and-server-logs
|
|
I just upgraded the demo to 4.7.2 and still cannot reproduce.
Definitely going to need app logs. |
|
Dumb question on this one, how? |
https://snipe-it.readme.io/docs/common-issues#section-quick-tip-handy-commands
|
|
@Jarli01 those errors in your error log are from 2017 |
|
@Jarli01 try this instead: https://snipe-it.readme.io/docs/whoops#section-tailing-a-log-file-on-linuxosx If you tail the file then trigger the select box again, relevant errors should appear on your screen
|
|
|
Try deleting the contents of your |
|
(Also, this error looks weird to me - it wouldn't trigger an actual email to be sent if you haven't actually checked it out yet.) |
|
I don't send emails on checkout, just weekly asset reports/ audits etc. Dir for /vendors? |
|
|
Wait wait - |
|
glad I was waiting, also was going to just move the fold and then run it |
I don't know what that means. |
|
I was going to move the folder to vendor-bck and then run |
|
want to jump on gitter and see if we cant find a fix? |
|
Tried all of these, except the (composer clear-compiled) that did not work and problem persists. composer dump-autoload |
|
@Jarli01 I'm about to go to lunch, so I can't. You can certainly rename the folder instead of deleting it, it doesn't matter - I just want to force composer to re-download the dependencies. We've already got customers on 4.7.2 (and the demo works), and we haven't caught any errors in our logging systems, so I suspect this is a cached vendor, view, etc somewhere that's interfering with your individual local installs. As I said tho, the exceptions you pasted have to do with mailing things, not checking out, so I don't think those errors are related to what you're seeing. |
|
@sabait - you need to include the http:// or https:// in front of the URL. Try changing it and then running |
|
|
|
@Jarli01 that's very helpful, thank you. That's a network-level error. Snipe-IT doesn't have anything to do with whether or not your names resolve. What's the URL you use to access your Snipe-IT install? |
That fixed it for us! |
|
@snipe Adding Http:// and running the php artisan config:clear actually fixed it fot me. |
|
A local dns address. I can see if the issue persists by accessing it at the IP address. |
|
Same result accessing it from the IP. |
|
|
|
@Jarli01 - your APP_URL must match whatever base URL you use to access your Snipe-IT install. If you access it at
(Be sure to clear your config cache when you update this. Under APP_URL: |
|
That url is just a dns mask, but I'll update and try, anything after |
|
Still getting the same message about |
|
From firefox private mode
|
|
Try updating with the IP in your .env instead and clear your config cache. CORS errors are a browser-error that means the browser doesn't like that the javascript calls are coming from a different domain than the originating request. (Remember to start it with http:// or https://, and clear your config cache) |
|
Still no change |
|
To clarify: If the URL of your dashboard - not what you enter into the browser, but what the URL bar in the browser eventually redirects to - is |
That was understood. In the above .env screenshot that is what I showed http://snipeit.farts.com |
|
|
|
Okay, again, name not resolved means that whatever you have in your APP_URL isn't something that can rue resolved via the browser. That's not a Snipe-IT thing, that's a DNS thing. |
|
Someone in gitter who just built brand new is having the same issue edited because the links don't work that way. . . from gitter to here. |
|
We had the same issue and I just fixed it by correcting our Just wanted to share this to make sure that those using |
|
@Jarli01, |
We use the |
|
@n0creativity yea, I can ping the full address without issue. |
|
So, to sum up.... In v4.7.0+, we manually inject the baseUrl that's used by the javascript. This variable pulls directly from the .env file, which means a few things:
I've just pushed out a change to master that should resolve these edge-case issues. |
2 tasks
|
Thanks @snipe. Changed my app url from http to https to resolve :) |
|
Thanks @snipe. I updated the app_url in the .env and all appears to be right with the world. |
snipe
added a commit
that referenced
this issue
Aug 15, 2019
* Fixes #6204 - added email alerts and web/API access to assets due for audits (#6992) * Added upcoming audit report TODO: Fid diff/threshold math * Added route to list overdue / upcoming assets via API * Controller/API methods for due/overdue audits We could probably skip this and just handle it via view in the routes… * Added query scopes for due and overdue audits * Added audit due console command to kernel * Added ability to pass audit specs to main API asset search method * Added audit presenter * Added bootstrap-tables presenter formatter to display an audit button * Added gated sidenav items to left nav * Added audit due/overdue blades * Cleanup on audit due/overdue console command * Added language strings for audit views * Fixed :threshold placeholder * Removed unused setting variable * Fixed next audit date math * Added scope for both overdue and upcoming * Derp. Wrong version * Bumped version (I will release this version officially tomorrow) * Leave the activated state for users alone in normal LDAP synchronisation. (#6988) * Fixed #7003 - crash when warranty months or purchase date is null * Fixed #6956 - viewKeys policy inconsistent (#7009) * Fixed #6956 - Added additional gates show showing/hiding license keys * Modified gate to allow user to see licenses if they can create or edit the license as well * Added API middleware to API routes to enable throttling TODO: Figure out how to make this costumizable without touching the code * Import locations from CSV via command line (#7021) * Added import locations command * Small fixes to location importer * Added country, LDAP OU * Cleaned up comments, added more clarification to what the script does * Added ability to update groups via API Fixes [ch9139] * Bumped version * Fixed #6883 - remove escaping of fields on LDAP import * Fixed #6880 - correctly encrypt encrypted fields via the API * Fixes #5054: LDAP users deactivated for none-ad (#7032) When using none-AD ldap, users are automatically deactivated every LDAP sync. This commit changes the behaviour so that if the active flag isn't set, the users are enabled. Fixed #5054, at least for 4.X * Updated packages - Updating erusev/parsedown (v1.7.2 => 1.7.3): Downloading (100%) - Updating squizlabs/php_codesniffer (3.4.1 => 3.4.2): Downloading (100%) - Updating symfony/polyfill-mbstring (v1.10.0 => v1.11.0): Downloading (100%) - Updating symfony/var-dumper (v3.4.23 => v3.4.27): Downloading (100%) - Updating league/flysystem (1.0.50 => 1.0.51): Downloading (100%) - Updating symfony/translation (v3.4.23 => v3.4.27): Downloading (100%) - Updating nesbot/carbon (1.36.2 => 1.37.1): Downloading (100%) - Updating symfony/debug (v3.4.23 => v3.4.27): Downloading (100%) - Updating symfony/console (v3.4.23 => v3.4.27): Downloading (100%) - Updating symfony/finder (v3.4.23 => v3.4.27): Downloading (100%) - Updating symfony/polyfill-ctype (v1.10.0 => v1.11.0): Downloading (100%) - Updating symfony/polyfill-php70 (v1.10.0 => v1.11.0): Downloading (100%) - Updating symfony/http-foundation (v3.4.23 => v3.4.27): Downloading (100%) - Updating symfony/event-dispatcher (v3.4.23 => v3.4.27): Downloading (100%) - Updating symfony/http-kernel (v3.4.23 => v3.4.27): Downloading (100%) - Updating symfony/process (v3.4.23 => v3.4.27): Downloading (100%) - Updating symfony/routing (v3.4.23 => v3.4.27): Downloading (100%) - Updating symfony/polyfill-util (v1.10.0 => v1.11.0): Downloading (100%) - Updating symfony/polyfill-php56 (v1.10.0 => v1.11.0): Downloading (100%) - Updating symfony/psr-http-message-bridge (v1.1.1 => v1.1.2): Downloading (failed) Downloading (100%) - Updating rollbar/rollbar (v1.7.5 => v1.8.1): Downloading (100%) - Updating symfony/yaml (v3.4.23 => v3.4.27): Downloading (100%) - Updating symfony/browser-kit (v3.4.23 => v3.4.27): Downloading (100%) * Fixed #7044 - API update deleted custom fields if they are not re-presented * Fixed XSS vulnerability when creating a new categories, etc via modal on create Same fix as before, because of the weird select2 post-parsing ajax behavior * Updated email strings * Fixed #7046 - added user website url back into UI * Updated language strings * Bumped version * Updated packages * New backups config for spatie * Removed debugbar service provider (autodiscovery) * Use laravel v5.5 withCount manual aliases * Added spatie language files * Removed old laravel backups config This config file was renamed in a newer version of spatie laravel-backup * Set the serialization * Added the command loader to console kernel * Renamed fire() to handle() * Updated withCount to use manual naming * Updated backup path in backup admin * Updated travis with new php versions * Bumped laravel version in readme * Fixed custom field edit screen * Fixed baseUrl is undefined error I literally cannot figure out how this ever worked before. * Fix for included files in backup * Bumped version * Switch has() to filled() * Change ->has() to ->filled() * Removed cosole log * Bumped packages * Use getReader instead of fetchAssoc for CSV parser https://csv.thephpleague.com/9.0/upgrading/ * Handle JSON validation errors like 5.4 * Handle JSON validation errors like 5.4 * Handle JSON validation errors like 5.4 * Trying to fix ajax asset validation This I think gets us closer, but still not handling the validation on the asset properly. When I do a print_r of the validation in the other items, its looking for an error bag that looks something like this: ``` Illuminate\Support\MessageBag Object ( [messages:protected] => Array ( [name] => Array ( [0] => The name field is required. ) [seats] => Array ( [0] => The seats field is required. ) [category_id] => Array ( [0] => The category id field is required. ) ) [format:protected] => :message ) ``` Currently the Assets ajax returns: ``` [2019-05-24 06:52:06] develop.ERROR: array ( 'messages' => array ( 'model_id' => array ( 0 => 'The model id field is required.', ), 'status_id' => array ( 0 => 'The status id field is required.', ), 'asset_tag' => array ( 0 => 'The asset tag field is required.', ), ), ) ``` So not sure why it’s not working. * Fixed missing asset validation * Check that a model exists before trying to fiddle with fieldsets * Tidied up license check * Removed extra escaping on checkin * Updated importer to work with newer CSV Reader::getRecords() method * Fixed field mapping * Small fix for reordering fields Fixes Illuminate\Database\QueryException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'order' cannot be null (SQL: insert into `custom_field_custom_fieldset` (`custom_field_id`, `custom_fieldset_id`, `order`, `required`) values (12, 7, , 0)) [ch1151] This needs revisiting for a more solid fix, especially for data that was already entered bad. * Fixed bug where sorting by company name in Users API did not work Fixes [ch9200] * Removed custom fields from AssignedSearch to prevent confusing data in selectlist Fixes [ch9193] * Removed alert-danger from tests * Fixed missed consumables_count withCount() statement * Fixed Undefined variable user in $backto if checked out to a non-user Fixes [ch9194] * Check for valid model before attempting to access fieldsets Fixes [ch1249] * Only build the log upload destination path if there is a matching record Fixes [ch1232] * Fixed free_seats_count variable name (I forgot that Laravel switched camel case to snake case for their old 5.4 withCount variables) * Only gtry to delete the file if a record is found in the log * Only try to get fieldset if model is valid * Fixed more camel-casing -> snake-casing * Only display the file if the log record can be found * Fixed casing in sync command * Updated README * Derp - typo * Added link to Atlassian plugin * More Atlassian clarifications * Show accessory image on view page * Increased image size to 800px, added lightboxes * Fixed #7083 - Removed user_exists constraint on department save If the user has been deleted, this prevented the department from being successfully saved on edit * Updated branch in version file * Dockerfile update to bring us up to php v7.1 for Laravel 5.5 (#7084) * bump up to php7.1 & change deprecated MAINTAINER to a LABEL so it is visible with `docker inspect` * AND modapache >< * 2 updates required to get software-properties+ppa * Bumped version * Bumped release again :( * Missed one * Fixed #7098 - updated backup config for deleteFile() method * Fixed #7092 - handle weird port forwarding/port numbers for baseUrl * Bumped version * Fixed #7099 - set email to null by default for backup notifications * Removed old comments * Fixed #7100 - Check if $user isset on checkin * Increased throttle to 120 requests per minute * Added Filipino, corrected order for Spanish variations * Update language strings * Bumped hash * Changed has to filled to fix bulk asset editing * Bumped point version * Small fixes for phpleague CSB reader v9 * Improved error checking in locations importer * Fixed #7145 - rename groups table to permissions_group for mysql 8 reserved word compatibility * Reduce minimum group name length to 2 (from 3) eg: IT * Back in time fix FOR #7145 for new installs on MySQL 8+ * Fixed permission insert //TODO Handle this via model * Possible fix for reporting/admin migration back in time * Fixed #7164 - change table name to permission_groups * Fixed LDAP password blanking on save * fixing previous commit's actual wiping of password (#7183) replaced Input::fille('ldap_pword') with _filled_. Should be good to go. #7179 #7169 * Bumped version * Downgrading rollbar for Laravel 5.5 * Spelling Correction (#7206) Fixed Spelling for the word reqrite, to be rewrite. * Fix #6910: Add logic to manipulate the eloquent query. (#7006) * Added company_id to consumables_users table * Added logic to manage when a pivot table doesn't have the column company_id trough a join with users * Remove a migration that tries to fix this problem, but is not longer necessary * Addresses #7238 - add PWA code to layout Needs additional UX testing * Better log message for bad LDAP connection * Fixed #7186 - has vs filled in User’s API blanking out groups if no group_ids are passed * Comment clarification on #7186 * Check for valid seat on hardware view * Added space between footer and custom message * Cap warranty months to three characters Filles rollbar 209 * Cap warranty months to 3 on the frontend blade * Fixed countable() strings on user destroy * Check that the user has assets and that the aset model is valid * Bumped hash * Caps asset warranty to 20 years * Command to fix custom field unicode conversion differences between PHP versions (#7263) * Fixes #7252 form request changes (#7272) * Fixes for #7252 - custom fields not validating / no validaton messages in API w/form requests * Removed debug info * More fixes for #7252 This is mostly working as intended, if not yet the way Laravel wants us to do it. Right now, the API returns correctly, and the form UI will return highlighted errors, with the input filled in ~sometimes~. I’m not sure why it’s only sometimes yet, but this is potentially progress. * Removed experimental method * Check for digits_between:0,240 for warranty * Removed debug code * Apply fix from PR #7273 to master * Bumped hash * Fixed #7250 - permission issue for API fieldsets and fields endpoints This applies the change from #7294 to master * Add @mskrip as a contributor * Fixed #7270 - Checking-in Assets via API Removes the Item's Asset Name * CORS for api (#7292) * Added CORS support to API * Changed order so CORS will still work if throttle hit * Added APP_CORS_ALLOWED_ORIGINS env option * Fixed typo * Clarified header comments * More clarification * DIsable CORS allowed origins by default to replicate existing behavior * Change variable name to be clearer * Bumped version * Added condition to deal with fieldname 'rtd_location' which can be tried to be queried in some places and doesn't exist in database (#7317) * Added comments to the ByFilter query scope for clarity * Added accessories checkout/checkin API endpoint * Fixed CVE-2019-10742 https://nvd.nist.gov/vuln/detail/CVE-2019-10742 * Update README.md (#7334) Add reference to CSV importer. * Group related variables in .env * History importer fixes * Fixes to history importer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please confirm you have done the following before posting your bug report:
Describe the bug
When I attempt to check out an asset to the user, there is a drop down menu that contains all of the users from the organization using the LDAP sync. However, after updating, the list merely says, 'the results could not be loaded.' I have restarted everything on my end.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A list of users in the organization should populate the list.
Screenshots
If applicable, add screenshots to help explain your problem.
Server (please complete the following information):
Desktop (please complete the following information):
Smartphone (please complete the following information):
Error Messages
storage/logsand your webserver's logs.Additional context
Is this a fresh install or an upgrade? Upgrade
What OS and web server you're running Snipe-IT on
What method you used to install Snipe-IT (install.sh, manual installation, docker, etc) Git Bash
Include what you've done so far in the installation, and if you got any error messages along the way.
Indicate whether or not you've manually edited any data directly in the database
Add any other context about the problem here.
Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.
The text was updated successfully, but these errors were encountered: