Navigation

Pligg Support

I want to add to my pligg website this link

https://groups.google.com/forum/#!forum/lets-make-a-wahtsapp-clone

but appear this

URL is invalid or blocked: https://groups.google.com/forum/#!forum/lets-make-a-wahtsapp-clone

Why ? and how i can fix that ?

Possible Answers

    The reason I think is it's a bug in Pligg, rather than a "secure link". You can submit Google login page, Github login page, etc.

    Pligg will blocked or invalidate URLs with exclamation point ( ! ). Take away the exclamation point from that Google URL and it will be accepted.

    | Posted 132 days ago | Permalink | Hide Replies

    Thanks oxyThemes for bringing up this issue. I did some research about why #! is used in the URL. It appears that it is meant for crawlers to indicate that the value after the #! is a dynamic content. you can read all about it here:

    https://developers.google.com/webmasters/ajax-crawling/docs/specification

    However, the whole process of this is beyond the scope of how to fix the issue in Pligg code.

    Removing the ! does not work all the times. What needs to be done is working on the regex that validates the URL upon entering the link and pressing submit. I believe I made some progress with that but still need to test some more.

    | Posted 131 days ago | Permalink | Hide Replies

    Nice catch on that one Oxy!

    I was thinking the problem came after the story was entered (when the link was clicked). Never thought about Pligg itself rejecting the well formed URL.

    Maybe using a URL shortener service to generate a new URL from that one would allow the URL to work from Pligg. Not a great fix but would allow a working solution until a code fix could be created.

    | Posted 132 days ago | Permalink | Hide Replies

    Because it is a secure link and you must be signed in to the group to have access to it. When you navigate to the link, you get this message:

    Lets make a wahtsapp clone

    You must be signed in and a member of this group to view and participate in it.

    Sign in to view this group

    | Posted 133 days ago | Permalink | Hide Replies

    after carefully dissecting the url validation pattern in /submit.php, I made some additions to validate the hash-bang #! and changes to the order of characters that were wrong.

    the new validation pattern validates well. I tested it on a lot of urls and it validated properly:

    The links below start with "http(s) | ftp

    "foo.com/photos.php?id=1111111#!/photo.php?pid=719397&id=1111111&fbid=111111110"

    "foo.com/?ref=home#!/pages/foo-foo/888888888?v=wall&ref=ts"

    "foo.com/foo.foo#!/profile.php?id=100000&v=wall"

    "fairuziyet.com/song.php?

    song=%D8%AD%D8%A8%D9%8A%D8%A8%D9%8A%20%D9%82%D8%A7%D9%84%20%D8%A7%D9%86%D8%B7%D8%B1%D9%8A%D9%86%D9%8A&alpha=%D8%AD&page_no=1"

    "fairuziyet.com/song.php?song=نحنا والقمر جيران&albnum=1&playnum=1&musinum=1&page_no=2"

    "1337.net"

    "a.b-c.de" (only validates in the test but not on pligg)"

    "foo.bar/?q=Test%20URL-encoded%20stuff" (only validates in the test but not on pligg)"

    "j.mp"

    "foo.bar/baz"

    "code.google.com/events/#&product=browser"

    "☺.damowmow.com/" (only validates in the test but not on pligg)"

    "secure.wikimedia.org/wikipedia/en/wiki/Alan_Turing#Early_computers_and_the_Turing_test"

    1- Open submit.php

    2- Look for function do_submit1() { (it should be line 136 if you have not modified the code)

    3- Add $url = utf8_decode($url);

    right after $url = html_entity_decode($url);

    it will make sure the encoded urls are properly decoded.

    4- Comment the pattern on line 197

    do not delete any code, just comment it in case you want to revert back to it.

    5- Add this new pattern below the commented one

    $pattern = '/^(([w]+:)?//)?(([dw]|%[a-fA-fd]{2,2})+(:([dw]|%[a-fA-fd]{2,2})+)?@)?([dw]([.-dw]{0,253}[dw])?)+[w]{2,4}(:[d]+)?(([/#!+-_~.,dw]+|%[a-fA-fd]{2,2})*)*(??(&?([-+_~.,dw]|%[a-fA-fd]{2,2})=?)*)?(#([-+_~.,/dw]|%[a-fA-fd]{2,2})*)?$/';

    I will submit it on github too to be assessed.

    | Posted 129 days ago | Permalink | Hide Replies

    Here's a similar issue for this problem: https://github.com/Pligg/pligg-cms/issues/153

    | Posted 129 days ago | Permalink | Hide Replies

Who Upvoted this Story

Who Downvoted this Story

Pligg.com's Support area is where you can ask questions and get answers. Just getting started with the Support area? This section describes tips for participating.

Submitting a Question or Comment

By taking a minute to research previous posts you may receive an answer much faster than waiting for a response to a new question. Begin by searching the support section for an answer. Sometimes you may even want to extend your search to the entire pligg.com domain.

If you are unable to find a relevant answer, submit a new question or comment here. Please provide a detailed description and, when necessary, debugging information such as your server environment (a link to a <?php phypinfo(); ?> .php page would be very helpful), your web browser, and any steps necessary to reproduce your issue.

Submitting an Answer

If you have an answer or useful response that you would like to add to a post, you can submit it as a comment which other users will then vote on. Answers are sorted by most popular to least, allowing the best information to climb to the top of the page.

Please read and vote for existing answers before submitting your own, as there may already be an acceptable answer provided. You can use the "Reply" link found within an answer to submit a response to it, in case you want to expand or comment on someone else's contribution.

Including Files or Code

Sometimes it is necessary for you to attach a file or include a snippet of code for others to reference in your response. In most cases, you can .zip up files and attach them to a question or answer using Pligg's file manager. At times though this may fail, and in these circumstances we recommend using a third party host. Below we are including a list of recommended websites where you can share easily share file uploads (or snippets of code) through the web.