[Steven Zahm]

@ Sharon

No, that is a WordPress error message when the roles assigned to the user attempts to access a page to which they do not have the permission to access. It is a WordPress security measure.

I know many users are quite successfully using Connections/Link with Wishlist, s2Member and others that I can’t think of off the top of my head at the moment. Personally, I am not at all familiar with any of the membership plugins but from my limited exposure to several on other users sites — they all seem to offer the ability to block the admin or specific admin pages or just pages in general depending on their membership, roles and capabilities. With that said, there must be settings that need changed in order to allow access. What exactly those are, I’m very sorry, but I’m not able to give you specific instruction.

Some good news…

I have released Form 2.0, this past Friday. I’m slowing getting the documentation updated. Link 2.0 is also complete. When I’m finished with the form docs, I’ll release Link 2.0. With those two combined, they enable front-end entry user addition and maintenance. The exact release date will wholly depend on how much time I spend in these support forums … however, if you have Form, I suggest updating to 2.0 and since you have Link, I can email you an advanced copy. just let me know.

[Steven Zahm]

@ Lori

You can use categories to split up directories.

The most common way of doing this is with cMap or any of the other *Plus templates. See this FAQ.

Here’s another support topic where another user is asking for something nearly identical. Similar instructions will work for you too.

I hope that helps.

[Steven Zahm]

@ carolin

Yes, that is correct.

If you have a moment, I would truly appreciate a review as they do make a difference. Many thanks in advance!
http://wordpress.org/plugins/connections/

[Steven Zahm]

@ Daniel

Ok, looks like the server is IIS 6 … that’s pretty old. If you do not have access the the IIS config, then your host will have to make the change necessary to the rewrite rules in order to remove the index.php from the URL (that the website address in the browser address bar).

See the last post in this support thread, they are a few links which may help.
http://wordpress.org/support/topic/removing-indexphp-from-my-urls#post-4433162

Sorry that’s the best I can do because this is a web host issue. There’s nothing I can do to fix it, sorry.

[Steven Zahm]

@ cheryl

In short, the issue should correct itself after you site goes live with a domain name. But if you’d like to fix it, here’s how:

The document root can not be determined automatically. So you have to manually set the DOCUMENT_ROOT here’s how:

Add the following to the timthumb-config.php file found here:

../wp-content/plugins/connections/includes/libraries/timthumb/

This is what you need to add, make sure to change the doc root accordingly:

define ( 'LOCAL_FILE_BASE_DIRECTORY', '/my/doc/root/' );

What /my/doc/root will be will depend entirely on the server setup. If you go to the the Connections : Dashboard admin page and look at the the System widget; there will be a constant named CN_PATH. The doc root should be the beginning portion of that path. What I can tell you is that from the wp-content and on will NOT be part of the doc root.

Hope that helps.

[Steven Zahm]

@ Daniel

Can you please share a link to the page having the issue so I can take a look? Thanks!

[Steven Zahm]

@ Will

Sorry, no. I do have this on my feature request list, however with Form 2.0 front-end editing support and it’s Link 2.0 integration. It might not be possible to add.

[Steven Zahm]

@ Qasim

Can you reply back with a link to the page having the issue so I can see?

[Steven Zahm]

@ Mike

re: After installed cMap, it said successfully installed and it is existing in wp-content/connections_templates/cMap but nothing show up in admin connections>template section. I cannot activate.
What version of cMap did you attempt to install? If you are installing a really old version of cMap you might need to manually install the template. See the instructions on the bottom of this page. If you are installing a recent version of cMap, it is installed as a plugin, you do not install it using the legacy template installer.

re: I couldn’t find any template anywhere.
The old site, cMap can be found here:

../wp-content/blogs.dir/1/connections_templates/cmap/

re: what I have to customise order to be look like this?
You can copy the old customized version of cMap to the new site and use it.

re: Can I use the template without customizing in different page after customised for another page?
Speaking in terms of the old cMap on the old site, yes, change the name of the folder of the customized version of cMap, then open the meta.php file and change the template details. What you need to change will make sense after you open the file. Then you can use both the custom cMap and the original cMap at the same time on different pages.

I hope that helps.

[Steven Zahm]

@ Will

re: The docs are a bit sparse so after install, ended up here in the forums.
Yeah, there’s really nothing to configure and it does it’s thing in the back ground.

re: This extension is really not very helpful – for two reasons.
Yes, for your use case.

re: Is there any possibility of this changing in the near future?
In short, yes. Link 2.0, if Form 2.0 is installed will allow front-end editing. I just released Form 2.0 on Friday. This week, I plan on updating all the documentation for Form. Then afterwards, release Link 2.0 and then update it’s documentation – there’s actually a little more to explain in setting up especially with the Form integration. Actually the setup is very simple, there’s just one item that can be confusing if not explained thoroughly. With From installed a user could still submit entries, which are not linked to them while also allowing them to add/edit an entry which is. Basically the setup is to turn off the “Submit New Entry” action in Form. Link will add its own add/edit entry link.

If you want, I can email you an advanced copy of Link. It is feature complete and only small tweaks are expected.

Oh, w/ Form 2.0, no dedicated page is required and no shortcode is needed. The shortcode will still work. I left it in only for backward compatibility. Form will now have it own “virtual” page.

[Author]

Posts