Topic-icon Dynamic url in request

Active Subscriptions:

None
11 years 3 months ago #51479 by [email protected]
I would like to add requests to my event pages via easy tags in the templates.

The challange i have is that the destination url for front end request needs to be the page from which the request was sent. I can create a static thank you page.

Basically i need it to work similar to like. I cannot create separate requests for every event as it would be too cumbersome.

Thanks
The topic has been locked.
Support Specialist
11 years 3 months ago #51507 by alzander
Replied by alzander on topic Dynamic url in request
JFBConnect doesn't currently support dynamic URLs for the Facebook Requests feature. The way our requests feature works, the request is created one time and the destination is stored with that request. Each time it's sent, we don't have a way to store a new redirection path for the receiver.

I can create a static thank you page.

The static thank you page, or some other static page to redirect to for the request, is what we'd recommend you do.

I hope that helps,
Alex
The topic has been locked.
Active Subscriptions:

None
11 years 3 months ago - 11 years 3 months ago #51526 by [email protected]
is this something we can look into for next version? im sure many have similar needs.

From a backend admin, I would have no problem configuring new request urls. But we populate lots of new events a week and our userbase invites.

So from a front end, if once the request module is clicked it would be have something like..
is a manuallly created ID specified in the module or easy tag y/n => if Y the proceed as normal => if no, check does front end reference exist? if yes, use settings from reference if not Create a new id & front end reference and use that.

A front end reference would contain something like
Full source frontend URL --
request Id

for this to work, you would need the ability to specify a default thank you page for all dynamic IDs in the config and it would be required, as we would populate it. It would also be nice to show the dynamic table as read only in the config area. If a dynamic ID needs to be overridden the workflow would be to simply create a manual one and specify it, as it takes precedence.

The only real requirement is that the page the module references must have unique URLs. there may be some off cases where this does not happen but looks like its kinda rare for most free and commercial extensions.

I am not a coder guru and its been a very long time since i truly wrote code, but seems to me this implementation shouldnt be too dificult.

i think this would be a really appreciated feature by many.

If you wanted to round out the complete feature set.
Instead of showing dynamic table as read only in backend,
[ul}Set only the request ID and Full URL read only
Add the description field as read write on backend ( you can even prepopulate with page meta if you choose)
Add a selection box for each record on the view and allow backend invites like the regular ids[/ul]
Last edit: 11 years 3 months ago by [email protected].
The topic has been locked.
Support Specialist
11 years 3 months ago #51537 by alzander
Replied by alzander on topic Dynamic url in request
The 6.3 release is locked in place, feature-wise, and should be released in March. A large change like this definitely won't be in that release.

As for when it could be implemented, it's something that's on our to-do list. However, we've had our Requests feature for about 2 years now. When first implemented, we had a few users looking for what you're asking for, but honestly haven't had such a request in over a year. That means it's a lower priority task for us.

Your overview seems correct, but I'm not sure I'm understanding everything you want it to do. For:

if yes, use settings from reference if not Create a new id & front end reference and use that.

Would that just go to the current page?

The only real requirement is that the page the module references must have unique URLs. there may be some off cases where this does not happen but looks like its kinda rare for most free and commercial extensions.

I'm not sure what you mean by this either.

Beyond that, there's quite a few new configuration settings and various checks and balances that would need to be done along with database table updates. This would not be a 'quick' update by any means. It's also something we'd have to do in a way to make sure it doesn't break current sites and all those 'kinda rare' situations always come and bite us.

In general, we'd love more feedback on what you're thinking, but please don't expect us to have a solution any time soon on this. For now, all we can recommend is having a good landing page that all invitations can go to and use that.

I hope that helps, and keep us posted with your thoughts,
Alex
The topic has been locked.