Chronoconnectivity gives a warning when I use at database view as tablename. I am able to save the form anyway. I found that a column of the view must be "id".
In the Connections Manager connections list the Show data link works, but the Link link does not. The page is not rendered properly. Only the Header is shown and no menus and other stuff from the site is shown.
To reproduce the problem do the following: Create a view in the database as simple as:
create view v_users(id,name) as select id,name from jos_users;
The header section contain: "TEST HEADER"
The body contains: "TEST BODY{name}<br>"
The Footer contains: "TEST FOOTER"
It should not be a prerequiste to always have a primary key if you don't need to edit.
Supporting views is a very powerful feature and I cant's see why it shouldn't work.
Is this something that can be solved within ChronoConnectivity?
Thanks
Sven
In the Connections Manager connections list the Show data link works, but the Link link does not. The page is not rendered properly. Only the Header is shown and no menus and other stuff from the site is shown.
To reproduce the problem do the following: Create a view in the database as simple as:
create view v_users(id,name) as select id,name from jos_users;
The header section contain: "TEST HEADER"
The body contains: "TEST BODY{name}<br>"
The Footer contains: "TEST FOOTER"
It should not be a prerequiste to always have a primary key if you don't need to edit.
Supporting views is a very powerful feature and I cant's see why it shouldn't work.
Is this something that can be solved within ChronoConnectivity?
Thanks
Sven