Support has been upgraded!
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
06/19/2014 at 8:56 am #294322
Well, the good news is I finally replicated the issue … I working finding the issue and will fix and release updates ASAP. I’ll reply back the second I figure out the issue and again when I release any updates that might required.06/19/2014 at 9:44 am #294329
Ok, I found the issue. It seem the page hook provided by WordPress can change depending on the role capabilities the user has assigned to them. Link hooks into certain page hooks in order to know when to load and display its metaboxes. So the fix was to update Link to add the other WordPress page hook. I just uploaded Link 2.0.1, please update to this version as I’m confident that this will address the issue for all.
You can download the update from your purchase history or if you entered your support license key on the Connections : Settings admin page under the Licenses tab, WordPress will notify you of the update and you’ll be able to update in your WP admin.06/19/2014 at 10:10 am #294333
re: What I wanted and expected, was, that I can make a link (Edit entry/ with shortcode?) on the frontside so that the user edit his own details in a nice Form.
If I use the “View MDE” options is is visible on all pages with the connections (i.e. EGTA/Bestuur (excerpt), Educatie/Docenten (market/siteshot), Leden/Ledenlijst (slim-plus)) which is not desirable. Therefor I did not use the “Result (List) Actions or Entry Actions” options.
I see… yes, that does complicate things a bit. I can add shortcode and possibly a widget that can be placed in the theme’s sidebar (only to be shown when a user is logged in). The catch will be, all the edit links would have to be resolve to the page set as the directory home page. This page does not have to exist in your page menu structure on the site but it will have to exist. I can also add a shortcode to the view entry and add it as an option to the widget but there is no way that I can think of where it would point to correct page on your site for the user logged in, it too would have to resolve to the directory home page. This would probably confuse your users so I’m not sure that would be useful to you at all.
Any way, if I add the shortcode and widget, would that meet your needs?06/19/2014 at 10:28 am #294335
@Steven, I think that’s what I mean.
The Directory Homepage is now also not visible in the page menu structure (Persoonlijke kaart)
The idea is that there is one directory and on three pages, different views, but editing is on another page which has the edit form.
Users are not allowed to add entry’s, only edit their own.
I hope it is possible. Thank you.
BTW, your service is second to none!06/19/2014 at 11:36 am #294365
Thanks for Link 2.0.1 the Edit My Directory Entry has now all the fields, but there is another issue…. the private/public radio button is gone. See image.
And more a question: if I am correct the Edit MDW is on the back end and the View MDE is on the front end (with Form of course). But the View MDE generates another entry, for example: if my name is Steven Subscriber (!) and I change it to Steven Subscriber Jr. on the View Form front-end, it creates an new entry (Steven Subscriber Jr.) See image. Instead of View MDE it has become Add New Entry. Is that what it is mend to do?
As far as I can see, it is still not possible to edit on the front end
Sorry for the inconvenience.
Attachments:You must be logged in to view attached files.06/19/2014 at 12:58 pm #294408
Sorry for the long post, but please take the time to read it thoroughly as I think it’ll help.
re: the private/public radio button is gone.
Right. There can only have access to the options the role has permission to to view as set on the Connections : Roles admin page. When I was developing Link 2.0, I originally limited the entry visibility too. But I decided when editing in the admin the user can change the visibility status of the entry. Depending on feedback, I may change this in later revisions to Connections and Link.
When editing with Form on the front-end, there will only be permitted to chose the visibility status that they have permission to view. Because if the user would chose a status they do not have permission to view, they would lose front-end editing altogether. They would simply get an error message saying they do not have permission to view the/their entry.
re: still not possible to edit on the front end
The “Edit My Directory Entry” link in the admin bar will always take one to the edit page in the admi.
The “View My Directory Entry” link in the admin bar will always link to the user’s entry in the front end.
The “Add My Directory Entry” link in the admin bar will only show to the user if there has not been an entry linked to them. This link will always link to the edit page in the admin page.
The “View My Entry” link in the list actions will always link to the the users entry in the front-end. If there is no entry linked, the user will instead be presented with:
The “Add My Directory Entry” link in the list actions will either link to the admin edit page or the Form submit page depending on if Form is installed and active.
The “Edit My Directory Entry” link in the entry actions will either link to the admin edit page or the Form submit page depending on if Form is installed and active.
The “Submit New Entry” link in the list actions will always be shown and always link to the Form submit page. This link has no relation to the adding/editing of “linked” entries, rather it allows the submission of “anonymous” entry submissions. It was a tough choice to leave this active when both Form and Link are installed because one of the core features of Form is to allow submissions to the directory. I may change this behavior/remove it when both Form and Link are installed depending on feedback. It makes sense how it is now when you think about it, but I definitely see how there will be confusion.
Now, I know you said you are not using the list action link or the entry action links because of your setup. So I’m not exactly sure how you submitted the entry you show in the screenshot. My guess is you simply went to the page with Form on it (added to the page with the legacy shortcode), yes? That will not work for adding/editing a linked entry. That’s why the action links exist… The shortcode is supported for backwards compatibility only for new submissions into the directory.
To edit an existing linked entry in the front-end without using the action links, visit the specific entry and then type
/edit/at the end of the address. That link will resolve to the edit page for the entry using Form.
Your setup is more “complex” than the majority of the users of Connections and these extensions. It’s a setup I’m willing to officially support which is why I’ll add the shortcodes and widget which can be used in lieu of or in addition to the action links.06/19/2014 at 2:03 pm #294420
Thanks for your long explanation, it’s quite clear to me now, and it even makes sense to me :-) Ergo: the subscriber has to use the admin bar or I have to activate the “Edit My Directory Entry” link in the entry actions. Clear!
Your interpretation of my screenshot was exactly how it was.
As you said you’ll make a shortcode and widget soon. Can’t wait for it.
Keep up the good work!06/19/2014 at 2:52 pm #294436Matthew CovingtonParticipant
Issue resolved. Very grateful!06/20/2014 at 6:00 am #294556Tom NiekampParticipant
Update works! thx a lot.
Tom06/20/2014 at 8:43 am #294570
@ Matthew, @ Tom
Great to hear. Apologies for the trouble and thanks for your patience!
You cannot reply to this support topic. Please open your own support topic.