Hi Thomas,

I was able to reset my old Apache account and have checked in my changes. I was able to keep your TurbineHtmlHead and body attributes with the new layout. However, I still have a couple issues.

I did some research and discovered the torque datasql task was removed quite a while back by Thomas fox, and while it looked like it was on target for the torque generator it was never completed (unless you know otherwise). https://issues.apache.org/jira/browse/TORQUE-24

Also - after building the sample app, I tried to complete the login/user authentication using the default LoginUser action and it does not seem like the user is ever authenticated. I will try to debug some more.

I added a folder "docs" to store the readme.txt and some sample data ready for insert (I used the old torque generator to build the turbine security sql). I inserted manually, launched the app and the login does not work.

Thanks,
Jeffery




On 10/23/2016 04:52 PM, Jeffery Painter wrote:
Hi Thomas,

I am not sure if I have commit access to the repo. It has been many years since I was last involved with the project. I will take your recommendations and try to update some tomorrow. I could also look at the torque test code. It took me a while to figure out how the new secure screen/action was supposed to work (since turbine 2.3 days), but I found most of that in test code as well for the Turbine security implementation with fulcrum.


Thanks,
Jeffery


On 10/23/2016 01:48 PM, Thomas Vandahl wrote:
Hi Jeffrey,

On 21.10.16 23:56, Jeffery Painter wrote:
I spent several hours working on cleaning up a bit more to make this a
little more friendly "out of the box" when someone invokes the archetype.
One more thing: I appreciate your attempts to provide a better styling
to the sample application. However would it be possible to keep the
#TurbineHtmlHead() and #TurbineHtmlBodyAttributes() somehow in the
layout as a best-practice recommendation?

Bye, Thomas.



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to