Jeremy Wallis

Hi folks … this is taking really long to finalise … when can you finish the code?
Thanks.

You previously assisted with this edit but you have since done an update on the code for me to permit front-end category editing and now it doesn’t work. i.e. people who are logged in can view files that they do not have permission to download. Not sure whether to post here or in the thread where you are trying to get the front-end category editing feature to work.

Thanks.

Thanks, I’ve just been to check it out, comments:

When adding a new category it now requires you to select a parent category so that you cannot create a top level category, that’s great, thanks!

The dialog box used to add the new category has lost the words ‘Parent Category’ though, so it’s not obvious what the dropdown box is about, could you add the Parent Category text back in?

I tested adding a sub-category to the Trustees category and then adding a document to that new sub-category and the document added fine.
When I tried to download the document though, it said that I don’t have permission to download it, so presumably the permissions of the parent category are still not being inherited by the new subcategory?

Thanks.

Any news?

Hi, It’s been a week since you last communicated about finalising the work, can you please update me?
Thanks.

Hi folks, any news on the final edits?
Thanks.

Just a heads up that I have moved the website to a different server today and will have it up and running soon. I first have to ensure all the right Apache & PHP modules are installed and working before the site will be ok’ed for use.

And so I will post as soon as I can with the revised server details … if you can then get that last requirement working = newly added categories (done from the front end) inherit the role view permissions of the parent (top level) category.

Apologies if you tried anything the past 48 hours, hopefully not.

Thanks.

When I added a doc to the category Test3, I ticked the category box for the category Test3 as part of the package creation process.

My assumption was that the sub-category would inherit the view permissions of the parent category, which it doesn’t seem to do.

As mentioned in the first comms:

– I set up the three top level folders and give permissions to them, all on the backend.

– And if people create categories on the front end within these top level categories, the new categories need to inherit the top level permissions in terms of roles who are permitted to view. Otherwise they would need back end access and that defeats the objective of them creating them on the front end.

So it’s almost there now … it just needs the permissions inheritance function to happen?

Can you also please fix the typo … the placeholder for Add Category and the confirmation message of ‘category has been added’ both spell ‘Category’ as ‘Categroy’
Thanks.

OK, many thanks. I have restored the backup and confirmed that all the functions I mentioned that had stopped working after your edits, have been confirmed as all working again.

Hopefully you can do the Add On route without it affecting any of the existing shortcodes used on the site as, as mentioned, I have done some minor edits to hide certain elements on the Add Docs page and allowing all approved users to see each others files, not just their own.

Many thanks.

You have changed what the short code for the front end does and so this has changed existing instances where it was used and then the other pages now don’t work as I detailed, for whatever reason. They all worked fine before you started.

Perhaps log back in and confirm what I am saying so you can see for yourself?

If you cannot resolve this I will have to install the backup I did just before you started and then we still need you to add the functionality of only being able to edit categories on the front end, nothing else.