https://twill.io logo
Powered by
# ❓questions
  • i
    of course if you use the same blocks in 2 modules it will reuse the same config, no need to duplicate it
  • u
    oh cool 😄
  • u
    i moved this crop to twill.php but i cannot render it in front
  • u
    still i have empty block
  • i
    the parameters you're using are not correct in the frontend. The first one is the name of the image role (the name of the form field, which must correspond to a key under twill.block_editor.crop), and the second is the name of the crop, not the name of the ratio. Can you paste what you put in twill config?
  • u
    i see.. now is working
  • u
    thanks
  • b
    Hi folks, wondering if you can help me. Followed the steps to upgrade my local install to 2.5.2 (from 2.40) and running into a couple of issues; 1. When trying to navigate to an edit page, I am getting the attached error. Is there something I have missed? 2. Also as I was upgrading from 2.40 I thought I might need to complete some of the steps for 2.50 and I am getting an error when trying to run 
    php artisan migrate
    . Any ideas? Do I need to do this?
    Copy code
    Migrating: 2019_02_17_173805_create_twill_users_tables

   Illuminate\Database\QueryException 

  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'twill_users' already exists
    p
    • 2
    • 2
  • u
    how can i pick Metadata editing (alternative text, caption) from image used in block?
  • u
    to use it in block/image.blade.php
  • c
    As the block model has the Has Medias trait you can use any of the methods defined in that trait https://twill.io/docs/api/2.x/A17/Twill/Models/Behaviors/HasMedias.html
  • c
    So you'd use $block->imageAltText($role)
  • c
    so in your example it would be $block->imageAltText('image')
  • u
    ok, it should be work.. but what with caption etc?
  • u
    i can check it by self cmd?
  • u
    like block:list
  • u
    can some how the hell i get 404 when i have controller and routes..
  • u
    Copy code
    <?php

namespace App\Http\Controllers;

use App\Repositories\PostRepository;
use Illuminate\Http\Request;

class PostController extends Controller
{
    public  function __construct(PostRepository $repository)
    {
        $this->repository = $repository;
    }

    public function index()
    {
        // $posts = Post::where('published', '1')->get();

        return view('blog.index', [
            'posts' => $this->repository->blog()

        ]);
    }

    public function show($slug)
    {

        $post = $this->repository->forSlug($slug);
        abort_unless($post, 404, 'Post');
        return view('blog.show', compact('post'));
    }
}
  • u
    Copy code
    <?php

namespace App\Repositories;

use A17\Twill\Repositories\Behaviors\HandleBlocks;
use A17\Twill\Repositories\Behaviors\HandleTranslations;
use A17\Twill\Repositories\Behaviors\HandleSlugs;
use A17\Twill\Repositories\Behaviors\HandleMedias;
use A17\Twill\Repositories\Behaviors\HandleTags;
use A17\Twill\Repositories\Behaviors\HandleRevisions;
use A17\Twill\Repositories\ModuleRepository;
use App\Models\Post;

class PostRepository extends ModuleRepository
{
    use HandleBlocks, HandleTranslations, HandleSlugs, HandleMedias, HandleTags, HandleRevisions;

    public function __construct(Post $model)
    {
        $this->model = $model;
    }

    public function blog()
    {
        return $this->model->published()->orderBy('created_at', 'desc')->get();
    }
}
  • u
    Copy code
    <?php

use Illuminate\Support\Facades\Route;
use App\Http\Controllers\PageController;
use App\Http\Controllers\PostController;

/*
|--------------------------------------------------------------------------
| Web Routes
|--------------------------------------------------------------------------
|
| Here is where you can register web routes for your application. These
| routes are loaded by the RouteServiceProvider within a group which
| contains the "web" middleware group. Now create something great!
|
*/



Route::get('/', function () {
    return view('home');
});

// podstrony
Route::get('/{slug}', [PageController::class, 'show']);

// blog

Route::prefix('blog')->group(function () {

    Route::get('/', [PostController::class, 'index']);
    Route::get('/{slug}', [PostController::class, 'show']);
});

// Route::get('/blog/{slug}', [PostController::class, 'show']);
// Route::get('/blog', [PostController::class, 'index']);
  • p
    error-after-twill-update
  • p
    I could be wrong, but I think your 
    Route::get('/{slug}', ...);
    is too generic. It should probably be declared last, otherwise it would have precedence over e.g. 
    /blog
    .
  • u
    i see.. but i want to make crud /{slug} and have some custom pages /custompage
  • p
    Try moving this line last, at the bottom of the file
  • u
    heh, its work..
  • u
    lol
  • u
    ❤️
  • d
    Hi @User and @User, i was wondering why my PHPStorm was marking the Method-Call 
    forSlug('some-slug')
    as wrong after updating to 2.5.2. So i checked the HandleSlugs.php where the DocBlock says $slug (first Parameter) has to be of type Array instead of string. Is my Method-Call wrong or just the DocBlock? 
    forSlugPreview
    is the same.
  • p
    Hey @User , you're right. This should be string and is totally my fault.
  • d
    Okay. Thank You. Should i create a Pull-Request or are you fixing it with the next release?
1...103104105...484Latest