ecards | Open Ecard Generator - Serverless | Runtime Evironment library

Add this rule on top of katiescards.com .htaccess file

In your config/queue.php file, which driver do you have set as the default?

For example: 'default' => env('QUEUE_DRIVER', 'sync')

(if you are using DotEnv then check the .env file in your docroot).

If you are using sync, it should send right away as sync is really only for development and will still block.

If you are using another method, like database, then you do have to ensure that your queues are configured to process how you expect.

Try running php artisan queue:work, then trigger your ajax call and it should send.

Both UICollectionViewCell and UITableViewCell are reused. As one scrolls off the top of the screen, it is reinserted below the visible cells as the next cell that will appear on screen. The cells retain any data that they have during this dequeuing/requeuing process. prepareForReuse exists to give you a point to reset the view to default values and to clear any data from the last time it was displayed. This is especially important when working with asynchronous processes, such as network calls, as they can outlive the amount of time that a cell is displayed. Additionally, you're doing a lot of non-setup work in awakeFromNib. This method is not called every time a cell is displayed, it is only called the FIRST time a cell is displayed. If that cell goes off screen and is reused, awakeFromNib is not called. This is likely a big reason that your collection views have the wrong data, they're never making their network request when they appear on screen.

EcardsCategoriesTableViewCell:

prepareForReuse should be implemented. A few things need to occur in this method:

• theseEcards should be nilled. When a table view scrolls off screen, you want to get rid of the collection view data or else the next time that cell is displayed, it will show the collection view data potentially for the wrong cell.
• You should keep a reference to the dataTask that runs in awakeFromNib and then call cancel on this dataTask in prepareForReuse. Without doing this, the cell can display, disappear, then get reused before the dataTask completes. If that is the case, it may replace the intended values with the values from the previous dataTask (the one that was supposed to run on the cell that was scrolled off screen).

Additionally, the network call needs to be moved out of awakeFromNib:

• You are only ever making the network call in awakeFromNib. This method only gets called the first time a cell is created. When you reuse a cell, it is not called. This method should be used to do any additional setup of views from the nib, but is not your main entry point in adding data to a cell. I would add a method on your cell that lets you set the category id. This will make the network request. It will look something like this:

The default order for a WebSecurityConfigurer adapter is 100 and you appear to have two in your application:

• com.sampleapp.myapp.ecards.MyApplicationConfiguration
• com.sampleapp.dep.dsp.core.autoconfigure.DsfCoreAutoConfiguration$DSFServerWebSecurityConfig

You should update one of them to be explicitly annotated with @Order, specifying a value other than 100. Given the limitations you've described, adding @Order to com.sampleapp.myapp.ecards.MyApplicationConfiguration seems to be more likely to be ok. Whether its order should be higher or lower will depend on the relationship between the the different parts of your security configuration and, if that configuration overlaps, which one you want to take precedence.

Make the following changes:

Generics are evaluated at compile time and assigned a single, concrete type. There is no such thing as "type inference at runtime."

I think the primary change you want is: