| # |
Jan 8th 2019, 16:32 |
slackebot |
<challgren> |
| # |
Jan 8th 2019, 16:30 |
 challgren |
Yeah thats what I figured out but in my BuildingUses table it does remove the above methods |
| # |
Jan 8th 2019, 16:29 |
dereuromark |
better to have one more than one less |
| # |
Jan 8th 2019, 16:29 |
dereuromark |
or dont run it with -r :slightly_smiling_face: not needed anyway usually to do so |
| # |
Jan 8th 2019, 16:28 |
dereuromark |
if you wanna keep them just add ! as comment - as documented |
| # |
Jan 8th 2019, 16:14 |
challgren |
Since I never use those directly in the Table class |
| # |
Jan 8th 2019, 15:52 |
slackebot |
$options = []) *``` |
| # |
Jan 8th 2019, 15:52 |
slackebot |
\App\Model\Entity\EnergyFixtureOption|bool saveOrFail(\Cake\Datasource\EntityInterface $entity, $options = []) * @method \App\Model\Entity\EnergyFixtureOption patchEntity(\Cake\Datasource\EntityInterface $entity, array $data, array $options = []) * @method \App\Model\Entity\EnergyFixtureOption[] patchEntities($entities, array $data, array $options = []) * @method \App\Model\Entity\EnergyFixtureOption findOrCreate($search, callable $callback = null, |
| # |
Jan 8th 2019, 15:52 |
challgren |
Then wouldn’t it remove ``` * @method \App\Model\Entity\EnergyFixtureOption get($primaryKey, $options = []) * @method \App\Model\Entity\EnergyFixtureOption newEntity($data = null, array $options = []) * @method \App\Model\Entity\EnergyFixtureOption[] newEntities(array $data, array $options = []) * @method \App\Model\Entity\EnergyFixtureOption|bool save(\Cake\Datasource\EntityInterface $entity, $options = []) * @method |
| # |
Jan 8th 2019, 15:52 |
challgren |
Ohh well that would be why |
| # |
Jan 8th 2019, 15:51 |
dereuromark |
it must be used inside the class its annotated on : $this->myMethod( etc |
| # |
Jan 8th 2019, 15:51 |
challgren |
Yeah in a QueueTask |
| # |
Jan 8th 2019, 15:51 |
dereuromark |
the current dev-master contains the fix to not remove if used. |
| # |
Jan 8th 2019, 15:50 |
dereuromark |
is it used? |
| # |
Jan 8th 2019, 15:29 |
slackebot |
<challgren> |
| # |
Jan 8th 2019, 15:28 |
challgren |
Nope still removing |
| # |
Jan 8th 2019, 15:26 |
dereuromark |
see changelog. nie find |
| # |
Jan 8th 2019, 15:26 |
challgren |
Ok I’ll “upgrade” |
| # |
Jan 8th 2019, 15:26 |
dereuromark |
@challgren check dev-master, I added some fixes here :slightly_smiling_face: |
| # |
Jan 8th 2019, 15:24 |
cnizzardini |
I'd at least like to get the actual exception class name so we can display better messages to end users. |
| # |
Jan 8th 2019, 15:23 |
cnizzardini |
( [message] => An Internal Error Has Occurred. [url] => /publisher/v3.0/book/preview.json [code] => 500 ) |
| # |
Jan 8th 2019, 15:23 |
cnizzardini |
Is there a way to get better error messages out of Cake 3.5 when debug is set to false. Exceptions from our api return this to our client: |
| # |
Jan 8th 2019, 15:22 |
challgren |
And I do use the importCsv function inside a QueueTask |
| # |
Jan 8th 2019, 15:19 |
slackebot |
\App\Model\Entity\BuildingUse|bool saveOrFail(\Cake\Datasource\EntityInterface $entity, $options = []) * @method \App\Model\Entity\BuildingUse patchEntity(\Cake\Datasource\EntityInterface $entity, array $data, array $options = []) * @method \App\Model\Entity\BuildingUse[] patchEntities($entities, array $data, array $options = []) * @method \App\Model\Entity\BuildingUse findOrCreate($search, callable $callback = null, $options = [])``` |
| # |
Jan 8th 2019, 15:19 |
challgren |
And then on my other plain Table it removes ``` * @method \App\Model\Entity\BuildingUse get($primaryKey, $options = []) * @method \App\Model\Entity\BuildingUse newEntity($data = null, array $options = []) * @method \App\Model\Entity\BuildingUse[] newEntities(array $data, array $options = []) * @method \App\Model\Entity\BuildingUse|bool save(\Cake\Datasource\EntityInterface $entity, $options = []) * @method |
| # |
Jan 8th 2019, 15:18 |
challgren |
It removes `@method array importCsv(string $content, $fields = [], $options = [])` |
| # |
Jan 8th 2019, 15:17 |
challgren |
@dereuromark the command is `bin/cake annotations all -r` |
| # |
Jan 8th 2019, 14:58 |
spriz |
just wanted to check if there is something obvious I’m missing :) |
| # |
Jan 8th 2019, 14:58 |
spriz |
Yeah that’s what I do as well |
| # |
Jan 8th 2019, 14:49 |
neon1024 |
Might be better to abstract it to a third party service perhaps, which provides an endpoint to see if the session still exists. It would add request overhead though, but would allow you to correctly manage the sessions in one place |
| # |
Jan 8th 2019, 14:48 |
neon1024 |
You’d kinda have to write the current session id to the db user record, so when they logged into the other site it could find the existing session. Although Cake might get upset, as you’d have to hook the login to prevent a new session being created. Plus you’d need to think about one site destroying the session, how it would effect the other |
| # |
Jan 8th 2019, 14:47 |
neon1024 |
No idea if that would work, but I don’t see why. It’s just hard to know which session to re-open on the other site |
| # |
Jan 8th 2019, 14:47 |
neon1024 |
As if you modified the session handler, or wrote your own you could save the sessions to a spot on the filesystem that both sites had access to |
| # |
Jan 8th 2019, 14:46 |
neon1024 |
https://book.cakephp.org/3.0/en/development/sessions.html#built-in-session-handlers-configuration |
| # |
Jan 8th 2019, 14:46 |
neon1024 |
> cake - Saves sessions as files inside tmp/sessions. This is a good option when on hosts that don’t allow you to write outside your own home dir. |
| # |
Jan 8th 2019, 14:46 |
ricksaccous |
i just know it's very do-able |
| # |
Jan 8th 2019, 14:46 |
neon1024 |
I think it’s file |
| # |
Jan 8th 2019, 14:46 |
ricksaccous |
not sure the best way actually |
| # |
Jan 8th 2019, 14:46 |
ricksaccous |
hmph |
| # |
Jan 8th 2019, 14:46 |
ricksaccous |
just feed that raw SQL statement to querybuilder |
| # |
Jan 8th 2019, 14:44 |
spriz |
what’s the best way to make Cake send `USE INDEX(indexName` with query builder? :slightly_smiling_face: |