Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello romca-
I am very happy that authors no longer have access to administer ejournal. Now, as an administrator, I can add a journal, but once I do, there is no "add issue" button. In fact, the old issue I had created seems to be completely missing (although the associated content nodes are still there), and the "Working Area" is completely gone. Any ideas?
Thanks-
KC
Comment | File | Size | Author |
---|---|---|---|
#8 | adminpanel.JPG | 47.13 KB | culvekd |
#8 | ejournaladmin.JPG | 25.58 KB | culvekd |
#3 | ejournal-admin-menu.jpg | 13.32 KB | nobios |
Comments
Comment #1
HyperD CreditAttribution: HyperD commentedIt requires Token that there is not in the package, as there is not in Drupal
Comment #2
chrysonline CreditAttribution: chrysonline commentedHi, from France.
Your documentation is good ! Thanks :-)
I try to add a journal with E-journal 6.x-1.0-alpha1 (under Drupal 6.6 with Token and Token actions 6.x-1.11.)
- i created a new type of content (myjournal) for E-journal
- i created a new taxonomy vocabulary for myjournal (with terms like : edito, reviews, news today...)
i confirm : there is no "add issue" button.
Missing. Any other idea ?
Comment #3
nobios CreditAttribution: nobios commentedWell, I alerady tried a few times and always get the add issue..
We have 2 main places for working with ejournal
admin/settings/ejournal - for general settings
admin/ejournal - for journal specific
Maybe you're looking in the wrong menu.
Comment #4
culvekd CreditAttribution: culvekd commentedI am actually using Drupal 5, and a few weeks ago Romca fixed a bug where authors and authenticated users could manage the issues-- the issue number, whether it was published, etc. He published the latest version as a fix and I notice two differences...the "Ejournal" menu item is gone from the right menu (it still appears under "site configuration," but this prevents authors from being able to access it), and when I go to Ejournal through Site Configuration, it allows me to add a journal, but there is no "add issue" button. Also, it will not allow me to delete a journal-- it comes back with "Array" when I try to delete.
Comment #5
romca CreditAttribution: romca commentedHi,
please try to rebuild the menu (with the devel module or simply by reinstalling some module or by running this from php block: menu_rebuild();)
What happens if you go to: http://yoursite.com/admin/ejournal/add/1/_/X ?
Comment #6
romca CreditAttribution: romca commentedTiziano,
I am not sure if I understand you. The Token module must be installed separately but it is listed as a requirement. Or is there perhaps some "token string" missing? Something that does not resolve?
Comment #7
chrysonline CreditAttribution: chrysonline commentednobios,
Thanks !
I found it :-)
Comment #8
culvekd CreditAttribution: culvekd commentedWhen I go to ...admin/ejournal/add/1/_/X it says "Access denied." I will try to rebuild the menu, but it seems strange that adminstrator can add journals (I've added two as tests), but can't delete journals (it says "Array" when I hit "delete"). I'm attaching a screenshot of the Ejournal admin (under "Site Configuration") to show that it doesn't offer "add issue" and a screenshot of the Administration panel to show that the "Ejournal" that used to be under "Content Management" (if I remember correctly) is gone.
Comment #9
romca CreditAttribution: romca commentedPls try the new rc2 release or the dev release
In ejournal, admin/settings/ejournal is for adding journals (publications)
admin/ejournal is for its management -- there oyu can add issues I admit, it can be confusing, but it has itw own reasons. Perhaps the links should not be the same "Ejournal"
one more thing, ejournalpathuato module is not yet ready (there should be no .info file), i noticed an error when deleting an issue caused by this module -- without it, everything works as expected
Comment #10
higherform CreditAttribution: higherform commented@romca -
I am also seeing the access denied to admin/ejournal for all user > uid = 1.
Our case:
Complex 5.x install, approx 40 modules, all working well (Centos, PHP 5.2.6, etc.)
Originally installed ejournal-5.x-2.0-rc2
Created new role "xxx chief editor"
Tried adding first only ejournal1_chief_editor permission, then generic Ejournal Chief Editor permission, etc until all Ejournal and ejournal1 permissions were set for that role. Tried removing ejournal1_author, no change
In every case, user 1 can access admin/ejournal, users assigned the "xxx chief editor" role get Access Denied page.
Installed 5.x-2.x-dev dated 2008-Nov-23, same results.
Installed ejournal-5.x-1.1 instead, access was allowed to admin/ejournal for the "xxx chief editor" role, using the same permission set that results in Access Denied in 5.x-2.*-* .
Hope this helps.
Comment #11
romca CreditAttribution: romca commentedhigherform,
many thanks for the info. it should be ok now (both in d5 and d6, i created new releases for them and dev will have them too - the packaging script will run at some point during the day or you can get it from cvs)
roman
Comment #12
higherform CreditAttribution: higherform commentedInstalled 5.x-2.x-dev dated 2008-Dec-21, access to admin/ejournal and subpages is working as expected for user > uid = 1 with role permissions set.
Comment #13
higherform CreditAttribution: higherform commentedComment #14
higherform CreditAttribution: higherform commentedNo new reports of this issue in over a month, I think its time to close it as fixed. Good work romca.