XML Parsing Error: XML or text declaration not at start of entity
Location: https://forum.userstyles.org/discussions/feed.rss
Line Number 2, Column 1:
<?xml version="1.0" encoding="utf-8"?>
^
This is an old issue, as far as I know, that was fixed. I just checked again and it works fine. Can you explain where you still see it?
Doesn't work. The code is not updated.
Again, I need more specifics like which style you're talking about, which OS, which device, maybe even even a screenshot, cause it's working for me.
Style: 107316 Google Chrome version: 54 OS: Windows 10 You can only update directly on the style page.
You can make an update now and tell me what you've updated so I can test it?
Using the default options, I updated lines 194 and 195.
Sorry, Justin. Lines 192 and 193.
Allow a suggestion: create a style, without any practical function, just for testing. Install it in Chrome. Then modify anything in the code (on the userstyles page) and try updating the style through the Chrome styles management page. You'll see that the code doesn't update.
Yeah, I was going to say yesterday that João is talking about the unrelated, pre-existing Chrome Style-Manager update bug, but then I noticed his posts were made in Firefox, so I figured that wouldn't make sense. Guess he is.
Yeah, I was going to say yesterday that João is talking about the unrelated, pre-existing Chrome Style-Manager update bug, but then I noticed his posts were made in Firefox, so I figured that wouldn't make sense. Guess he is.
Yes, I use only Firefox, but my style is more installed in Chrome and users can not update it.
Sure, makes enough sense. I just don't think Justin has been on the same page in regards to what issue you're describing.
You're right. I also think he still has not understood that this bug is very serious. After all, you create a style and launch updates. Users need to be warned of these updates, even better if they are automatic, as in firefox.
This is an old issue, as far as I know, that was fixed. I just checked again and it works fine. Can you explain where you still see it?
Doesn't work. The code is not updated.
Again, I need more specifics like which style you're talking about, which OS, which device, maybe even even a screenshot, cause it's working for me.
Style: 107316 Google Chrome version: 54 OS: Windows 10 You can only update directly on the style page.
You can make an update now and tell me what you've updated so I can test it?
Using the default options, I updated lines 194 and 195.
Sorry, Justin. Lines 192 and 193.
Allow a suggestion: create a style, without any practical function, just for testing. Install it in Chrome. Then modify anything in the code (on the userstyles page) and try updating the style through the Chrome styles management page. You'll see that the code doesn't update.
Seems like it's working for me. Here's the copied code from lines 192, 193:
This is an old issue, as far as I know, that was fixed. I just checked again and it works fine. Can you explain where you still see it?
Doesn't work. The code is not updated.
Again, I need more specifics like which style you're talking about, which OS, which device, maybe even even a screenshot, cause it's working for me.
Style: 107316 Google Chrome version: 54 OS: Windows 10 You can only update directly on the style page.
You can make an update now and tell me what you've updated so I can test it?
Using the default options, I updated lines 194 and 195.
Sorry, Justin. Lines 192 and 193.
Allow a suggestion: create a style, without any practical function, just for testing. Install it in Chrome. Then modify anything in the code (on the userstyles page) and try updating the style through the Chrome styles management page. You'll see that the code doesn't update.
Seems like it's working for me. Here's the copied code from lines 192, 193:
Yeah, I was going to say yesterday that João is talking about the unrelated, pre-existing Chrome Style-Manager update bug, but then I noticed his posts were made in Firefox, so I figured that wouldn't make sense. Guess he is.
Yes, I use only Firefox, but my style is more installed in Chrome and users can not update it.
This is an old issue, as far as I know, that was fixed. I just checked again and it works fine. Can you explain where you still see it?
Doesn't work. The code is not updated.
Again, I need more specifics like which style you're talking about, which OS, which device, maybe even even a screenshot, cause it's working for me.
Style: 107316 Google Chrome version: 54 OS: Windows 10 You can only update directly on the style page.
You can make an update now and tell me what you've updated so I can test it?
Using the default options, I updated lines 194 and 195.
Sorry, Justin. Lines 192 and 193.
Allow a suggestion: create a style, without any practical function, just for testing. Install it in Chrome. Then modify anything in the code (on the userstyles page) and try updating the style through the Chrome styles management page. You'll see that the code doesn't update.
Seems like it's working for me. Here's the copied code from lines 192, 193:
Updates from Userstyles.org now works. It was a caching issue and I just set it to refresh more often. Please check and confirm it's working for you now.
Regarding the update identification through the extension, I'm aware of the fix that is waiting in Github. I want to run testing on it before I release it, and I also want to creating a stg. environment so that what happened in the past few weeks won't repeat itself. I expect I'll be able to release it in a couple of weeks.
I think that sums up all the issues that followed the migration. If there's anything else let me know.
Updates from Userstyles.org now works. It was a caching issue and I just set it to refresh more often. Please check and confirm it's working for you now.
Regarding the update identification through the extension, I'm aware of the fix that is waiting in Github. I want to run testing on it before I release it, and I also want to creating a stg. environment so that what happened in the past few weeks won't repeat itself. I expect I'll be able to release it in a couple of weeks.
I think that sums up all the issues that followed the migration. If there's anything else let me know.
Google Chrome still can't "see" the updates made on userstyles.org. I tested it now and it didn't work. Updates are only possible directly on the site. Unfortunately, it's a very serious bug.
Updates from Userstyles.org now works. It was a caching issue and I just set it to refresh more often. Please check and confirm it's working for you now.
Regarding the update identification through the extension, I'm aware of the fix that is waiting in Github. I want to run testing on it before I release it, and I also want to creating a stg. environment so that what happened in the past few weeks won't repeat itself. I expect I'll be able to release it in a couple of weeks.
I think that sums up all the issues that followed the migration. If there's anything else let me know.
Google Chrome still can't "see" the updates made on userstyles.org. I tested it now and it didn't work. Updates are only possible directly on the site. Unfortunately, it's a very serious bug.
I know that and I answered that - said this is a legacy bug that I'll upload a fix for in the next couple of week. Read my post again, you'll see why.
My priority was to return Userstyles.org to its status before I made the migration of DB, which I did.
XML Parsing Error: XML or text declaration not at start of entity
Location: https://forum.userstyles.org/discussions/feed.rss
Line Number 2, Column 1:
<?xml version="1.0" encoding="utf-8"?>
^
@Jefferson I just tried with a new profile and it did not happen.
But what is strange is that as soon I disable Stylish the bar goes away, as soon I re-enable Stylish it is back...
Very strange bug, the bar is not part of XUL Firefox GUI and I can't inspect it to know from where it come.
When I enable Stylish I don't have any Userstyle for the page or for the Firefox GUI/XUL and no global style enabled.
:bz
I suggest you open a new thread sharing your used Userstyle and asking the community to help you figure it out. From what I see here, and given the fact I don't see this bug either, it's not an issue with Stylish, but rather with specific Userstyle/s.
I just posted this as its own thread: false alarms in style check when I uploaded my latest revision to my style. Did the CSS validation for userstyles.org contributions recently get added/updated?
I don't know if this is an isolated incident, but I'm having an issue with the style options.
I added a new one which fixes the alignment for certain users, and I have it set to off by default. My style automatically updated on my system and it added the setting. Additionally one of my users tried to install the style WITH the alignment but it did not add the changes.
Updates from Userstyles.org now works. It was a caching issue and I just set it to refresh more often. Please check and confirm it's working for you now.
Regarding the update identification through the extension, I'm aware of the fix that is waiting in Github. I want to run testing on it before I release it, and I also want to creating a stg. environment so that what happened in the past few weeks won't repeat itself. I expect I'll be able to release it in a couple of weeks.
I think that sums up all the issues that followed the migration. If there's anything else let me know.
Google Chrome still can't "see" the updates made on userstyles.org. I tested it now and it didn't work. Updates are only possible directly on the site. Unfortunately, it's a very serious bug.
I know that and I answered that - said this is a legacy bug that I'll upload a fix for in the next couple of week. Read my post again, you'll see why.
My priority was to return Userstyles.org to its status before I made the migration of DB, which I did.
I've just rebooted and upon opening Opera v42.xx (latest) I find Stylish (Chrome 1.6.1) keeps disabling itself. I click enable or reload and 5 seconds later is goes greyed out (extensions page).
This happened before last month a couple of times. This time no amount of browser close/restart or even reboot seems to fix it.
Any thoughts Justin?
** Seems to only occur once opted out of reporting style data back. Opt back in and all works.
Opera (latest) v42.0.2393.94 and current (Chrome) Stylish add-on (1.6.1), appears to always be playing catch up when applying a style to a page on opening in new tab ir page refreshing a tab.
For just 0.5-2 seconds you see the original web page theme. Since all styles are dark, this then shows you a flash of the bright orig web page before the style gets applied.
This first started to occur after first version of Opera 42 onwards.
Any thoughts Justin on what this might be. Is it something with opera v42> and a conflict with the add-on?
Sometimes when the manage styles page is open (Opera latest), I get the the Opera page crash saying 'Out of memory'. Then a refresh starts the add-on back up again. This is the chrome add-on working Opera. The Opera add-on does not get updated much and kinda sucks, so we use the chrome one.
But since Opera v42.xx onwards the add-on has been acting up a lot. Worries me I'll lose 100+ styles.
Comments
Lines 192 and 193.
Allow a suggestion: create a style, without any practical function, just for testing. Install it in Chrome.
Then modify anything in the code (on the userstyles page) and try updating the style through the Chrome styles management page.
You'll see that the code doesn't update.
body:not(.is_rtl1) .ui_tab_count:not(.ui_tab_count_red):not(:empty):before, body:not(.is_rtl1) .module_header .header_count:not(:empty):before, body:not(.is_rtl1) .ui_crumb_count:not(:empty):before, body:not(.is_rtl1) .ui_box_header_cnt:not(:empty):before, body:not(.is_rtl1) .page_block_header_count:not(#group_l_summary):not(#group_bl_summary):not(#group_activity_events_count):not(:empty):before {content: "(" !important}
body:not(.is_rtl1) .ui_tab_count:not(.ui_tab_count_red):not(:empty):after, body:not(.is_rtl1) .module_header .header_count:not(:empty):after, body:not(.is_rtl1) .ui_crumb_count:not(:empty):after, body:not(.is_rtl1) .ui_box_header_cnt:not(:empty):after, body:not(.is_rtl1) .page_block_header_count:not(#group_l_summary):not(#group_bl_summary):not(#group_activity_events_count):not(:empty):after {content: ")" !important}
I hope you fix this issue soon.
Regarding the update identification through the extension, I'm aware of the fix that is waiting in Github. I want to run testing on it before I release it, and I also want to creating a stg. environment so that what happened in the past few weeks won't repeat itself. I expect I'll be able to release it in a couple of weeks.
I think that sums up all the issues that followed the migration. If there's anything else let me know.
Unfortunately, it's a very serious bug.
My priority was to return Userstyles.org to its status before I made the migration of DB, which I did.
I'd like to subscribe to RSS feeds.
There is a Annoying Bug with Stylish and Firefox 50.
When you use the devtools and Stylish is enabled a dark gray bar appears at the bottom of the screen.
When you disable Stylish it goes away.
@Jefferson I just tried with a new profile and it did not happen.
But what is strange is that as soon I disable Stylish the bar goes away, as soon I re-enable Stylish it is back...
Very strange bug, the bar is not part of XUL Firefox GUI and I can't inspect it to know from where it come.
When I enable Stylish I don't have any Userstyle for the page or for the Firefox GUI/XUL and no global style enabled.
:bz
I just posted this as its own thread: false alarms in style check when I uploaded my latest revision to my style. Did the CSS validation for userstyles.org contributions recently get added/updated?
I added a new one which fixes the alignment for certain users, and I have it set to off by default. My style automatically updated on my system and it added the setting. Additionally one of my users tried to install the style WITH the alignment but it did not add the changes.
In short:
Updates automatically with wrong setting.
Doesn't add changes with fresh install.
This happened before last month a couple of times. This time no amount of browser close/restart or even reboot seems to fix it.
Any thoughts Justin?
** Seems to only occur once opted out of reporting style data back. Opt back in and all works.
Opera (latest) v42.0.2393.94 and current (Chrome) Stylish add-on (1.6.1), appears to always be playing catch up when applying a style to a page on opening in new tab ir page refreshing a tab.
For just 0.5-2 seconds you see the original web page theme. Since all styles are dark, this then shows you a flash of the bright orig web page before the style gets applied.
This first started to occur after first version of Opera 42 onwards.
Any thoughts Justin on what this might be. Is it something with opera v42> and a conflict with the add-on?
But since Opera v42.xx onwards the add-on has been acting up a lot. Worries me I'll lose 100+ styles.
Opera 'Out of Memory' page crash. Happens a lot.
Looking forward to your backing up options.