I'm using Laravel and Sentry (Sentinel), i'm new for laravel.
when i try to develop laravel with Sentry, there's something that stops me from doing so, it's hash
http://localhost:8000/users/4wnpje
and my question is, is hash is created just for user profile?
how I can make that hash to my product page? because my product page still show plain text
http://localhost:8000/products/12
could someone explain it to me please?
Related
I have a Laravel Vue application. The goal is to build a shop. Frontend and backend run on the same server. I don't use any authentication (so no registration etc.). Nevertheless I want to start a session for the user as soon as he comes to the website. So that the shopping cart of the respective user remains saved.
The workflow is roughly clear to me. I haven't really found anything specifically for this case. But I think that it is not only me. That's why I'm asking you. Could you please outline the process here. I use POST, GET, PUT and DELETE methods for manipulating the shopping basket.
Thanks a lot!
i dont know if i got your question right or not but in my case if i worked on shopping cart i have two method to save data the first one is to use vuex to store data but if i need this data to be exist if i refresh the browser i will use localStorage as it's exist for purpose like this or i will use reddis and each time the user add something to cart i will add it to reddis and when he remove it i will remove it from it
I have a client whose existing database implements sha3-512 using the hmac, and I am building a laravel app that will make use of their existing user data which is on sha3-512 hash. They have existing app already using same service. It means i have to make laravel to use sha3-512 instead of Bcrypt.
Anyone knows how I can achieve this feat?
I have looked and tried suggestion here
Changing Laravel 5.4 password encryption and table column names
But it did not work.
Thank you guys.
I've developed an app which fetches data from an API based on Laravel 5.5. The marketing landingpage of the app is based on Craft CMS Version 3. The marketing website and the API and the databases of both systems are running on the same server.
I want to generate landingpages for each row of table X of the Laravel database.
www.website.com/awesome-landingpage-about-{slug}
What is the best approach to realize this?
I don't want to fetch the data directly from Laravel's database
I don't want to synchronize the Craft CMS database with the Laravel (add/remove the rows from the laravel's database as entries to Craft)
It would be awesome to be able to have an entry-type "Landingpage" where we can optionally create a landingpage, referencing to an ID of the laravel table and add additional content for the landingpages.
Would be a JSON-API from Laravel to Craft CMS Plugin a good performant idea?
One option would be to use a Dynamic Route and just fetch the data from 127.0.0.1 (because same server) from the template file? Or is there a smarter way in Craft CMS?
Let's start of by:
"I don't want to fetch the data directly from Laravel's database"
I'm assuming you don't want to write code in CraftCMS to access another project's database. Good. IF you plan on having them do seperate jobs and use Laravel API for fetching data alone, let it handle it's own database.
"I don't want to synchronize the Craft CMS database with the Laravel (add/remove the rows from the laravel's database as entries to Craft)"
So, this is my question:
You want to be able to create landing pages based of Laravel's rows alone or based of Laravel's database row's and CraftCMS's?
It all comes down to how well you want to abstract both frameworks.
I would probably tell laravel to accept requests from authenticated user (a CraftCMS User) or from localhosts (from within the machine alone) and I'd create endpoints to add/remove/edit/get data at my disposal. I'd then fetch rows from Laravel and combine with my own (assume I'm the CMS).
Even in an intranet network, the request to tell laravel to access the database is longer than to access the database from CraftCMS, so you should expect a dependency between the two projects.
For point 3, you'll have to store information on each database about something. On CraftCMS's to store at least the ID's it's going to request to laravel and laravel will have to get an endpoint where it can insert new stuff, if you're planning on having additional content there.
I'm not entirely sure if I got the idea you're trying to show when you say "add additional content for the landing pages" but I'd try to keep it simple and abstract it's uses, Laravel to store this 'information' that the CMS shouldn't handle in the first place (or you can work out some extra tables and import them to the other database).
Impact performance? Depends on the ammount of data you've got
I'ts just for practice and I need how to set up an Auth in Laravel but in the same table User. I know I have to use the default model User.php. I added my new column "type" where here I'm going to manage common users and admins. I edited and migrated that, also according to docs I created my guards and register providers but I don't know whats next. I know how to do it with another table but in the same table I have no idea how. I don't know how this Laravel's files works.
I have a quite large application written in Codeigniter 1.7.
It needs some significant enhancements and I have been evaluating Laravel 4 as the PHP framework.
I am trying to find out if anyone has successfully extended an existing Codeigniter application using Laravel so that some screens are Laravel and some are Codeigniter.
I imagine that authentication (currently using Ion Auth) and Session management (using mysql backend) would be two major hurdles to overcome.
If this is an option then I will explore in more detail as the amount of legacy code needing transferring is considerable.
Thanks in advance.
I suppose in your Laravel routes file, create a route for every page you have written in CodeIgniter. Route everything to the URL that CodeIgniter is expecting and as you complete portions in Laravel, change the routes to point to the correct ones Laravel expects as you go.
Before you do anything though, I'd get everything you need for authentication finished in Laravel, turn authentication off in CodeIgniter, and just let Laravel handle that in the routes.