hi!
I'm using the tweet_news plugin on my install, but currently it is creating a shortened URL when it tweets. Now I don't really need this,so would be nice to remove it, but if I can't, then how do I fix the header errors that the shortened URLs produce?
if you view the website outside of the shortened URL then there are no errors. an example of the error can be seen here: Notice: class-album detected an invalid folder name: tiny. in /home/ccphoto/public_html/zp-core/class-album.php on line 70
Notice: class-album detected an invalid folder name: tiny. in /home/ccphoto/public_html/zp-core/class-album.php on line 70
Warning: Cannot modify header information - headers already sent by (output started at /home/ccphoto/public_html/zp-core/class-album.php:70) in /home/ccphoto/public_html/index.php on line 123
Warning: Cannot modify header information - headers already sent by (output started at /home/ccphoto/public_html/zp-core/class-album.php:70) in /home/ccphoto/public_html/index.php on line 124
Warning: Cannot modify header information - headers already sent by (output started at /home/ccphoto/public_html/zp-core/class-album.php:70) in /home/ccphoto/public_html/index.php on line 125
Warning: Cannot modify header information - headers already sent by (output started at /home/ccphoto/public_html/zp-core/class-album.php:70) in /home/ccphoto/public_html/index.php on line 126
Comments
So when do you exactly get these errors? When you tweet or when someone visits your site via that tinyurl?
Example links would really be helpful.
Additionally please also try a standard theme in case this is theme related (no idea why though).
I changed this round to: RewriteRule index/.php$ index.php [L,QSA]
And now it appears to have resolved those issue, and loads the site correctly now. Not noticed anything else a problem so far either
I did never notice any issues and so far you are the first to report it. Htaccess is a complicated thing for sure so maybe we should investigate that. Please open a ticket about that so we don't forget it. Please post info about your server config as well (we once had an issue older vs newer apaches which took quite long to find out).