Re: [pylons-discuss] Re: docs down?
https://twitter.com/PylonsProject/status/1253465539512393729 --steve On 4/23/20 at 1:53 PM, sydo.luci...@gmail.com (Sydo Luciani) pronounced: > Cloudflare had network and DNS problem. > > https://www.cloudflarestatus.com/ > > Philadelphia services seems to be rerouted, but the reroute seems not > working. > Philadelphia, United States - (PHL)Re-routed > > > > > > > Someone needs to contact Cloudflare otherwise they think it is fixed. > > > On Thursday, 23 April 2020 15:30:00 UTC-5, Jonathan Vanasco wrote: > > > > I'm getting 403 errors from cloudflare on all the > > https://docs.pylonsproject.org urls. i tried accessing from several > > networks in the usa to ensure it wasn't a local routing or blacklist issue > > > Steve Piercy, Eugene, OR -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/r480Ps-10126i-17E9FF5A9D664B2F89A7F8B70107EABF%40Steves-iMac.local.
[pylons-discuss] Re: docs down?
Cloudflare had network and DNS problem. https://www.cloudflarestatus.com/ Philadelphia services seems to be rerouted, but the reroute seems not working. Philadelphia, United States - (PHL)Re-routed Someone needs to contact Cloudflare otherwise they think it is fixed. On Thursday, 23 April 2020 15:30:00 UTC-5, Jonathan Vanasco wrote: > > I'm getting 403 errors from cloudflare on all the > https://docs.pylonsproject.org urls. i tried accessing from several > networks in the usa to ensure it wasn't a local routing or blacklist issue > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/5b3f9994-1482-4aa2-8a1b-9f4eb6b336af%40googlegroups.com.
[pylons-discuss] docs down?
I'm getting 403 errors from cloudflare on all the https://docs.pylonsproject.org urls. i tried accessing from several networks in the usa to ensure it wasn't a local routing or blacklist issue -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/e8021f24-9f2e-4775-928e-54ef8c26c581%40googlegroups.com.
Re: [pylons-discuss] Generating URL using request.resource_url
Apparently Pylon project hosted by Cloudflare and Cloudflare seems having
problem.
On Thu, 23 Apr 2020 at 11:33, Antonio Beamud Montero <
antonio.bea...@gmail.com> wrote:
> El 23/4/20 a las 7:31, Steve Piercy escribió:
>
> Further reading, from the sidebar in the Traversal chapter, "The Example
> View Callables Accept Only a Request; How Do I Access the Context
> Resource?":
>
> https://docs.pylonsproject.org/projects/pyramid/en/latest/narr/traversal.html
>
> Hi all, this page is raising a 403 Forbidden Error... Any problems with
> the server?
>
> Greetings.
>
>
>
> In view callables that accept only a request, the context resource
> found by
> traversal is available as the context attribute of the request object,
> e.g., ``request.context``.
>
> That chapter is gold for all things traversal, including twenty-seven
> eight-by-ten color glossy pictures with the circles and arrows and the
> paragraph on the back of each one.
>
> --steve
>
>
> On 4/22/20 at 9:27 PM, xiste...@0x58.com (Bert JW Regeer) pronounced:
>
> Pass the current context. It should have lineage and thus know how to get
> to where you are right now.
>
> request.resource_url(request.context, '@@create')
>
> Bert JW Regeer
>
> On Apr 22, 2020, at 14:05, Sydo Luciani
> wrote:
>
> Back to my original post, fixed the problem with stripping leading slash
> in request.path
>
> in jinja template:
>
> {% set stripped_path = request.path | replace("/", "", 1) %}
>
> And then passed stripped_path to request.resource_url:
> href="{{ request.resource_url(request.root, stripped_path, '@@create') }}
> ">
>
> Please let me know if there is more elegant(Pyramid) way solution.
>
>
> On Wednesday, 22 April 2020 11:01:22 UTC-5, Sydo Luciani wrote:
> Application is using hybrid of traversal and URL dispatch.
> Here is the code:
> https://github.com/SystematicD/pyramid_wikiz/blob/master/__init__.py#L33
>
>
>
>
>
> currently application working fine, but using session to save and passing
> around the coming_from_url or next_url is problematic in browsing
> application in multi tabs.
> here is the code that needs to be changed.
>
> https://github.com/SystematicD/pyramid_wikiz/blob/master/templates/top_nav_bar.jinja2#L34
>
>
>
>
>
>
> With appending the @@create to the end of full url, then traversed url
> always stay the same after clicking on create button and no need to save
> the url in session.
>
> Checking document for generating hybrid:
>
>
> https://docs.pylonsproject.org/projects/pyramid/en/latest/narr/hybrid.html#generating-
>
> hybrid-urls <
> https://docs.pylonsproject.org/projects/pyramid/en/latest/narr/hybrid.html#generating
> -
> hybrid-urls>
>
>
> it is not clear how to generate the current application full url.
>
>
> Thanks
>
>
> On Wednesday, 22 April 2020 06:39:46 UTC-5, Steve Piercy wrote:
> Are you using traversal or URL dispatch?
> It seems that you don't want to pass in a `resource` as the first argument
> to `resource_url`, so perhaps you want to use
>
>
> https://docs.pylonsproject.org/projects/pyramid/en/latest/api/request.html#pyramid.request.
>
> Request.route_url <
> https://docs.pylonsproject.org/projects/pyramid/en/latest/api/request.html#pyramid.request
> .Request.route_url>
>
> ?
> --steve
>
> On 4/22/20 at 2:18 AM, sydo@gmail.com <> (Sydo Luciani) pronounced:
>
> root + path be the resource but passing request.url as resource throws
> error: href="{{ request.resource_url(request.url , '@@create') }}">
> path = [loc.__name__ or '' for loc in lineage(resource)] AttributeError:
> 'str' object has no attribute '__name__'
>
> On Wednesday, 22 April 2020 04:11:00 UTC-5, Sydo Luciani wrote:
>
> tried href="{{ request.resource_url(request.url , '@@create') }}"> but
> didn't work and got below error: path = [loc.__name__ or '' for loc in
> lineage(resource)] AttributeError: 'str' object has no attribute
> '__name__' Then tried href="{{ request.resource_url(request.root,
> request.path , '@@create') }}"> that I got double slash problem. Need to
> generate full URL and then append @@create. root, request.path ,
> '@@create') }}"> On Wednesday, 22 April 2020 02:42:44 UTC-5, Sydo Luciani
> wrote:
>
> This code: href="{{ request.resource_url(request.root, request.path ,
> '@@create') }}"> Generates below URL:
> https://domain_name.com:6543/%2FDir_1%2FDir_2/@@create
>
>
> <
> https://systematicd.com:6543/%2Fwiki%2FDir_2/@@create
>
> >
>
>After
Re: [pylons-discuss] Generating URL using request.resource_url
El 23/4/20 a las 7:31, Steve Piercy escribió:
> Further reading, from the sidebar in the Traversal chapter, "The
> Example View Callables Accept Only a Request; How Do I Access the
> Context Resource?":
> https://docs.pylonsproject.org/projects/pyramid/en/latest/narr/traversal.html
>
Hi all, this page is raising a 403 Forbidden Error... Any problems with
the server?
Greetings.
>
> In view callables that accept only a request, the context resource
> found by
> traversal is available as the context attribute of the request
> object,
> e.g., ``request.context``.
>
> That chapter is gold for all things traversal, including twenty-seven
> eight-by-ten color glossy pictures with the circles and arrows and the
> paragraph on the back of each one.
>
> --steve
>
>
> On 4/22/20 at 9:27 PM, xiste...@0x58.com (Bert JW Regeer) pronounced:
>
>> Pass the current context. It should have lineage and thus know how to
>> get to where you are right now.
>>
>> request.resource_url(request.context, '@@create')
>>
>> Bert JW Regeer
>>
>>> On Apr 22, 2020, at 14:05, Sydo Luciani wrote:
>>>
>>> Back to my original post, fixed the problem with stripping leading
>>> slash in request.path
>> in jinja template:
>>> {% set stripped_path = request.path | replace("/", "", 1) %}
>>>
>>> And then passed stripped_path to request.resource_url:
>>> href="{{ request.resource_url(request.root, stripped_path,
>>> '@@create') }} ">
>>>
>>> Please let me know if there is more elegant(Pyramid) way solution.
>>>
>>>
>>> On Wednesday, 22 April 2020 11:01:22 UTC-5, Sydo Luciani wrote:
>>> Application is using hybrid of traversal and URL dispatch.
>>> Here is the code:
>>> https://github.com/SystematicD/pyramid_wikiz/blob/master/__init__.py#L33
>>>
>>
>>
>>>
>>> currently application working fine, but using session to save and
>>> passing around the coming_from_url or next_url is problematic in
>>> browsing application in multi tabs.
>>> here is the code that needs to be changed.
>>> https://github.com/SystematicD/pyramid_wikiz/blob/master/templates/top_nav_bar.jinja2#L34
>>>
>>
>>
>>>
>>> With appending the @@create to the end of full url, then traversed
>>> url always stay the same after clicking on create button and no need
>>> to save the url in session.
>>>
>>> Checking document for generating hybrid:
>>>
>> https://docs.pylonsproject.org/projects/pyramid/en/latest/narr/hybrid.html#generating-
>>
>> hybrid-urls
>> > hybrid-urls>
>>>
>>> it is not clear how to generate the current application full url.
>>>
>>>
>>> Thanks
>>>
>>>
>>> On Wednesday, 22 April 2020 06:39:46 UTC-5, Steve Piercy wrote:
>>> Are you using traversal or URL dispatch?
>>> It seems that you don't want to pass in a `resource` as the first
>>> argument to `resource_url`, so perhaps you want to use
>> https://docs.pylonsproject.org/projects/pyramid/en/latest/api/request.html#pyramid.request.
>>
>> Request.route_url
>> > .Request.route_url>
>>> ?
>>> --steve
>>>
>>> On 4/22/20 at 2:18 AM, sydo@gmail.com <> (Sydo Luciani) pronounced:
root + path be the resource but passing request.url as resource
throws error: href="{{ request.resource_url(request.url ,
'@@create') }}">
path = [loc.__name__ or '' for loc in lineage(resource)]
AttributeError: 'str' object has no attribute '__name__'
On Wednesday, 22 April 2020 04:11:00 UTC-5, Sydo Luciani wrote:
> tried href="{{ request.resource_url(request.url , '@@create')
> }}"> but didn't work and got below error: path = [loc.__name__ or
> '' for loc in lineage(resource)] AttributeError: 'str' object has
> no attribute '__name__' Then tried href="{{
> request.resource_url(request.root, request.path , '@@create') }}">
> that I got double slash problem. Need to generate full URL and
> then append @@create. root, request.path , '@@create') }}">
> On Wednesday, 22 April 2020 02:42:44 UTC-5, Sydo Luciani wrote:
>> This code: href="{{ request.resource_url(request.root,
>> request.path , '@@create') }}"> Generates below URL:
>> https://domain_name.com:6543/%2FDir_1%2FDir_2/@@create
>>
>> > >
>> After domain_name:port, there is a '/' and a '%2F' which
>> represents another '/'. double slashes after domain name,
>> causing problem in finding the right view and the result is
>> "page not found". Is there a workaround this problem ? Thanks
>>>
>>> Steve Piercy, Eugene, OR
>>>
