LivePreview and movement of assets causes error or page load #11358
Comments
|
I don't know how much this relates, but I just had the same error log after unpublishing a page. I couldn't call any pages until I published it again. |
|
Additional to my previous comment I, there also the page is restored to a working state either by calling the livepreview successfull (sometimes that also doesnt work) aside from publishing it again. |
duncanmcclean
changed the title
Can you provide your |
|
Yes, here it is: <?php
use Illuminate\Support\Str;
return [
/*
|--------------------------------------------------------------------------
| Default Cache Store
|--------------------------------------------------------------------------
|
| This option controls the default cache connection that gets used while
| using this caching library. This connection is used when another is
| not explicitly specified when executing a given caching function.
|
*/
'default' => env('CACHE_DRIVER', 'file'),
/*
|--------------------------------------------------------------------------
| Cache Stores
|--------------------------------------------------------------------------
|
| Here you may define all of the cache "stores" for your application as
| well as their drivers. You may even define multiple stores for the
| same cache driver to group types of items stored in your caches.
|
| Supported drivers: "apc", "array", "database", "file",
| "memcached", "redis", "dynamodb", "octane", "null"
|
*/
'stores' => [
'apc' => [
'driver' => 'apc',
],
'array' => [
'driver' => 'array',
'serialize' => false,
],
'database' => [
'driver' => 'database',
'table' => 'cache',
'connection' => null,
'lock_connection' => null,
],
'file' => [
'driver' => 'file',
'path' => storage_path('framework/cache/data'),
],
'memcached' => [
'driver' => 'memcached',
'persistent_id' => env('MEMCACHED_PERSISTENT_ID'),
'sasl' => [
env('MEMCACHED_USERNAME'),
env('MEMCACHED_PASSWORD'),
],
'options' => [
// Memcached::OPT_CONNECT_TIMEOUT => 2000,
],
'servers' => [
[
'host' => env('MEMCACHED_HOST', '127.0.0.1'),
'port' => env('MEMCACHED_PORT', 11211),
'weight' => 100,
],
],
],
'redis' => [
'driver' => 'redis',
'connection' => 'cache',
'lock_connection' => 'default',
],
'dynamodb' => [
'driver' => 'dynamodb',
'key' => env('AWS_ACCESS_KEY_ID'),
'secret' => env('AWS_SECRET_ACCESS_KEY'),
'region' => env('AWS_DEFAULT_REGION', 'us-east-1'),
'table' => env('DYNAMODB_CACHE_TABLE', 'cache'),
'endpoint' => env('DYNAMODB_ENDPOINT'),
],
'octane' => [
'driver' => 'octane',
],
],
/*
|--------------------------------------------------------------------------
| Cache Key Prefix
|--------------------------------------------------------------------------
|
| When utilizing a RAM based store such as APC or Memcached, there might
| be other applications utilizing the same cache. So, we'll specify a
| value to get prefixed to all our keys so we can avoid collisions.
|
*/
'prefix' => env('CACHE_PREFIX', Str::slug(env('APP_NAME', 'laravel'), '_').'_cache'),
]; |
|
I've just re-read your issue and noticed you're still on Statamic 4.47.0, which is no longer supported. Can you try updating to Statamic 5 and let us know if you're still experiencing the same issues? |
|
Sadly I cant because of this issue #11245 I couldn't find the reason behind this problem for now so I can't upgrade safely to Statamic 5. |
|
Okay! It's very possible the issue you're running into here has been fixed by changes in v5. If you're still running into this issue after upgrading to Statamic 5, let us know and we can re-open this issue. |
|
I'm back with the newest Statamic and the cases with that error have slightly changed. Moving a file did nothing, except that the file was not displayed shortly after. Now every time I clear the complete cache I get this error. Still until I call the live-preview inside statamic. Also I dont have the permission to re-open this issue. :D |
|
After trying a bit I can be more detailed: The error occurs after clearing the application cache. |
|
Re-opened. Now that you've updated, can you run |
|
Sure: |
|
After playing with the error for a while I noticed that |
|
Ok, I have played around some more and some errors before were due to permission problems. Sorry! But one thing still doesn't work as intended: I think starting with Statamic 5 (I didn't notice it before) it's possible to visit unpublished pages while being logged into the CMS by simply calling the url. Now after clearing the cache or composer install the call of said unpublished page leads to the LivePrevie.php:15 error. But not on other page, probably because of the statamic 5 upgrade. This now is of course vastly less important because a normal visitor shouldnt see the unpublished pages anyway. Reproducing:
|
Bug description
Every time I use the livepreview and then move an asset the no page call works anymore because of that error until I use the livepreview again (with a refreshed cms, because sometimes the preview doesnt work too).
How to reproduce
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: