by
KK » Wed Jul 01, 2015 10:18 pm
Thanks. Had a look at the site and really couldn't find anything anomalous.
I logged-in as super-admin and (from the front-end) could create a pad and a note just fine (you can check).
1.- when (as super admin) registered pads.php, it said:
error page not found "some path .html" (the file name was empty)
2.- same thing happened with notes.php
That is because of the following statement in both
- Code: Select all
<!-- and invoke snippet corresponding to the selected view -->
<cms:embed "views/pads/<cms:show k_matched_route />.html" />
- where the code above tries to embed a file named after the matched route.
The very first time you were installing there were no routes and so it tried to embed '.html' with the error message.
It is an innocuous thing and would happen only the very first time.
Actually, the tutorial assumes that you'd be building the template step-by-step (and not install the pre-coded one). Had you gone step-by-step this would never have happened. Anyway, as I said, it is of no import. Just ignore it.
3.- can't assign a pad to superadmin
Couldn't duplicate this issue. As I mentioned at the beginning, I logged-in as super-admin and could create my pads just fine.
4.- If I visit pads.php it says "page not found".
I think you must be trying to access the pads from within the admin-panel. Right?
See, now the default URL used by the admin panel is no longer recognized (try setting cms:match_route debug to '1' and see what is going on).
You'll be able to access your pads from the frontend (where it'll make sure that you are the owner of it).
5.- Oddly, test user can succesfully create and assign notes, and create pads.
Good. That shows the application is working as expected.
Hope it helps.
