Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report not Visible #4

Open
ChrstnMgcn opened this issue Feb 23, 2014 · 10 comments
Open

Report not Visible #4

ChrstnMgcn opened this issue Feb 23, 2014 · 10 comments
Labels

Comments

@ChrstnMgcn
Copy link

I've installed the extra on a couple of different sites on different server and haven't been able to get anything to load.

I'm logged in to the manager while visiting a front-end page with ?BLOODLINE=1 and nothing extra shows. Just the site.

Are there other dependencies?

It looks very helpful and I'd love to get it working. I've tried 1.0.0 and 1.0.2

@fireproofsocks
Copy link
Member

Try the variations: ?BLOODLINE=report or ?BLOODLINE=raw and check the javascript console.

It's tough to guarantee that things show because of how different sites can be. There are no dependencies, but I've had trouble making it work on every site as well, thus the variations in the report format. If you've got a caching layer like Varnish or something on your server, it'll be nearly impossible to use.

@manicko
Copy link

manicko commented Feb 26, 2014

the same for me ((

?BLOODLINE=report works for me but in this case I see the blank site page((
If ?BLOODLINE=1 I see site page but don't see the BLOODLINE layer or something

I tested on local server ruining with wamp and on the shared hosting - the same result always.
I don't see any errors or bugs in java console, in Apache or modx logs.

hope there will be a solution as the idea of the component is great

@fireproofsocks
Copy link
Member

Like I said: it is extremely difficult to have the HTML visible in every case here and I've been unable to make it visible in all cases, that's why there are the variations in the report formats. If you can give me access to your particular MODX site I can look at it in more depth.

@manicko
Copy link

manicko commented Feb 26, 2014

No problem, if this could help to make the component better, I can give you an access to the test site.

How can I send you user/password without sharing it here?))

@fireproofsocks
Copy link
Member

You can use the email in the composer.json in the repo

@fireproofsocks
Copy link
Member

Or, you could just attach your template here with a link to your assets (CSS/JS) -- I think maybe this is caused by a simple JS conflict.

@fireproofsocks
Copy link
Member

Merging Issue #5 here. The problem is when a static template is used, the output does not appear.

@ChrstnMgcn
Copy link
Author

I was able to get it to work on a new blank install. The main site I'm trying to get it to work on doesn't use static templates, but does use static snippets and chunks. Likely the same issue, but figured I'd throw that in for troubleshooting.

Thanks for continuing to look into it!

@fireproofsocks
Copy link
Member

I've confirmed that the behavior is limited to static templates. I've been mucking through the MODX source code and I still can't spot where this is going south. Madness.

The workaround is to use the "rude" report:

http://site.com/page.html?BLOODLINE=rude

@fireproofsocks
Copy link
Member

This is an ongoing problem which I think requires a more drastic solution. I think when BLOODLINE is triggered, Bloodline plugin needs to take over the entire page in all its output, then separately it needs to make an Ajax or iFrame request that gets all the data from the page. That way we can minimize the conflicts between the various page components and generate a more readable full-page report.

Also, check this animation out: http://cssdeck.com/labs/0fepasaigr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants