Can't update user information #2
Comments
|
I have also the same error |
|
Should be fixed now. There was an accessor that was changing the format of the date and I added a mutator to change it back. Looking at it again the 'created_at' should not have even been available when editing the user table so it has been updated in the seed file. To update that on your end, simply go into the Tools->Database, then click on the 'Edit Bread' for the users table. Uncheck the 'Edit' checkbox in the 'created_at' row and then update the BREAD. After that you should be good to go. Screenshot attached.
Thanks for checking this out and letting me know. I appreciate it. |
akazorg
added a commit
to akazorg/voyager
that referenced
this issue
Mar 5, 2017
akazorg
added a commit
to akazorg/voyager
that referenced
this issue
Mar 7, 2017
Closed
This was referenced May 15, 2018
fletch3555
pushed a commit
that referenced
this issue
May 30, 2018
…3058) * Don't register the dashboard widgets inside VoyagerDummyServiceProvider * Add dimmers method to Voyager class * Use the new Voyager::dimmers() method * Add `isAccessible` method to widget classes * Add dummy widgets to the config inside the WidgetTest * Update PHPDocs * Remove code that overwrites the dummy data config * Remove unneccessary property True is the default value * Update WidgetTest * Rename `isAccessible` to `shouldBeDisplayed` to make it more general * Remove WidgetTest with needed rendered html file * Remove old DashboardTest * Add widget stubs * Add Voyager unit test * Add Dashboard feature test * Update DashboardTest * Add abstract BaseDimmer class * Extend all dimmers with new BaseDimmer class * Remove unnecessary check from Voyager class
fletch3555
pushed a commit
that referenced
this issue
Jun 1, 2018
* Don't show a widget if it's not accessible for the current user #2 (#3058) * Don't register the dashboard widgets inside VoyagerDummyServiceProvider * Add dimmers method to Voyager class * Use the new Voyager::dimmers() method * Add `isAccessible` method to widget classes * Add dummy widgets to the config inside the WidgetTest * Update PHPDocs * Remove code that overwrites the dummy data config * Remove unneccessary property True is the default value * Update WidgetTest * Rename `isAccessible` to `shouldBeDisplayed` to make it more general * Remove WidgetTest with needed rendered html file * Remove old DashboardTest * Add widget stubs * Add Voyager unit test * Add Dashboard feature test * Update DashboardTest * Add abstract BaseDimmer class * Extend all dimmers with new BaseDimmer class * Remove unnecessary check from Voyager class * Apply fixes from StyleCI (#3253) * Define .no-sort * Move classes from `td` to `th`, remove same IDs Moved `.no-sort` from `td`s to the `th`. Removed `.no-click` because I didn't find it anywhere else in the repo. Tranfigured `#bread-actions` to `.bread-actions` because there cannot be duplicate IDs. * `id` to `class` because of 85c67e7 * Moved `.no-sort` from `td`s to the `th`. * th.no-sort, td.bread-actions * The database-tool doesn't use a Datatable * Remove .bread-actions * Make last column (actions) non-orderable * Make last column (actions) non-orderable and non-searchable * Rollback the changes * Rollback the changes * Rollback the changes * Remove a new line in the end * Pull Actions columns' title to the right
Closed
fletch3555
pushed a commit
that referenced
this issue
Dec 12, 2018
* Set default ordering for BREAD Control the default ordering for bread-browse by selecting an order-column and direction in bread-settings. Fixes #3222 * Correct alphabetical order in language-file * StyleCI fix * StyleCI fix #2 * All directions lower-case, correct URLs for server-side pagination * Also use direction for ordering * Add documentation * Add (proper) german translations
emptynick
referenced
this issue
in mattrabe/voyager
Dec 28, 2018
fletch3555
pushed a commit
that referenced
this issue
Dec 28, 2018
#3758) * - Added toggle to top of BREAD browse view if current model uses SoftDeletes - When toggle is clicked, redirect the user to ?showSoftDeleted={bool}, preserving existing query params - In VoyagerBaseController->index() apply ->withTrashed() only if model uses SoftDeletes and showSoftDeleted uery param is true * Add Restore aka "Undelete" feature * StyleCI conformance * Fix Event reference * Delete compiled .css file * Fix for ordering * Restore app.css * Remove getRelationships() * Use correct language-string * Remove getRelationships() #2 * Check permissions
|
This issue has been automatically locked since there has not been any recent activity after it was closed. If you have further questions please ask in our Slack group. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Whenever I try to edit an user I receive an
InvalidArgumentException in Carbon.php line 425.This probably is because Voyager/Laravel saves the created_at differently than expected, as indicated by
at Carbon::createFromFormat('Y-m-d H:i:s', 'January 28th, 2016 11:20 AM')andat Model->__set('created_at', 'January 28th, 2016 11:20 AM') in VoyagerBreadController.php line 220The text was updated successfully, but these errors were encountered: