Can't Find simplepie.inc in Version 1.3.1 - php

I am trying Simple Pie for the first time and I'm running into a problem. I downloaded the new 1.3.1 version and unzipped it. I set up everything according to the instructions (created the php and cache folders in my root directory, loaded the library and php auto-loader.php file into the php folder, and set the permissions to 755 on the cache folder). However, despite looking at every single file in the Simple-pie folder I can't find the simplepie.inc file. I have searched Google for someplace to find it but I can't find anything and I've searched on here for solutions but I don't see anything. Can someone please tell me where to get the simple-pie.inc file?
If version 1.3.1 doesn't include it how can people that download that version use the program?
Thanks in advance!

It does. It exists in the library folder.
However you should not include the autoloader.php (if you are using the stock download and not your own build)

Some of the documentation for SimplePie perhaps needs updating, a lot of the examples use the older versions and may not work with the most recent version, I know I had to do significant heavy lifting to get the News Blocks 2.0 demo to work. And it still doesn't do everything POPURLS does, SimplePie is a beginning not necessarily an end, but it does work, assuming you give it good feeds. Poorly formatted feeds ie feeds that do not conform to RSS or Atom standards can bring your playhouse crashing down.
I just have this in my news aggregator index.php:
require_once('../news/php/autoloader.php');
Eventually they updated their documentation and the default download.

Related

phpdoc does not update my documentation

phpDocumentor v1.4.4
Fedora 24
Command line: phpdoc -d ./docsrc -t ./output
I am running phpDocumentor on Fedora 24 and have successfully generated documentation for my project one time.
I added a docblock to a function, and ran phpdoc again. But the output has not been updated. I verified the time stamps of the files and they have been regenerated, but do not reflect the changes.
I subsequently made numerous changes, and reran phpdoc after each change, but the generated documentation does not update.
I erased all the output files, renamed the directory of the input files, in short have done all I can to persuade phpdoc to generate new documentation that reflects the changes to my php files to no avail.
It would seem that phpdoc is caching the output somewhere but I cannot find where. I searched every path on my disk containing phpdoc then searched for the word "cache" in each path but it does not occur.
I tried changing the template with the --template directive but it does not recognise this directive.
I have tried using the --force directive but it does not recognise this directive.
Can someone enlighten me?
Cheers,
Peter
This sounds like one of those times where I would just walk through the process from the beginning:
Am I modifying source in the ./docsrc directory tree? Verify by opening the source member in vi/vim/nano/some-other-editor just to be sure the source has changed.
Have I modified the source using the correct syntax? (Please post some code that shows documentation that isn't being updated)
Modify documentation in another file with a simple change and see if that simple change appears when I regenerate my documentation.
Am I explicitly --ignore-ing the file or directory I'm expecting to change? (You don't appear to be)
Do I have a phpdoc.xml or phpdoc.dist.xml file with an <ignore> directive? details
Do I have the necessary permissions to create/update files in the ./output directory?
After I've executed phpdoc -d ./docsrc -t ./output do I see the expected change when using vi/vim/nano/some-other-editor?
Is my browser caching previous versions of the documentation? (I know you've already ruled this out Peter, I'm just trying to make my answer complete)
This is EXACTLY one reason why I created PHPFUI/InstaDoc! The problem with most documentation is that it is static. While that is great for libraries that don't change, if you want to document your own code, guess what? It tends to change every day! With InstaDoc, you can see the documentation instantly on your local machine before you even check it in. InstaDoc creates the documentation when you request the page. It is hands down the fastest documentation system out there. Most documentation systems create static pages and brag about how fast they can create the documentation. But guess what? Who cares? What you want is to see the documentation of your current code base right now. Turns out it only takes a few seconds to scan through all the files of the libraries you are using. InstaDoc caches that information, so you only have a long scan (and then only seconds) the first time, or when ever you add a new library.
Once you have a library scanned, the documentation comes up instantly, since it uses PHP reflection classes to read the file and display the documentation. So that file you just modified, it is completely 100% documented. Don't like the comments, change them, refresh the page. See an issue, correct it, refresh the page. Notice something could be better? Refresh the page. Want to check out the docs on a PR? Easy, just delete the cached index and refresh the page.
InstaDoc is open source and still young. Check it out and submit comments or PR's if it does not meet your needs, but it is the future of documentation. It will also generate static files for high volume sites, but the most important feature is that it gives you an instant reflection of your just edited code, and that is what makes it awesome.

"Add as link" in Netbeans?

How can I (in the Netbeans IDE) add files as links, or point to existing files, kind of like a shortcut?
Visual Studio 2012 can do this, as shown in the following screenshot (found on Google Images - not mine).
I miss this feature in Netbeans. Copying my files over all the time is not an option, since I constantly improve my PHP library files, that are used across all other projects.
I am using the full version of Netbeans, and in this case, I am doing PHP development.
I am not sure that PHP is supposed to work like that, since its code is not compiled.
I could be completely wrong, and if I am, I'm sure someone else will educate us both.
What I've usually done is put the library in some directory and then add that directory to PHP's include path by adding this to php.ini:
include_path = "dir to your library"
And then I'd make sure that whatever class autoloader I was using was looking through the include path.
That said, I've more recently moved away from this, because a global library that changes often has caused me problems (a change would break something and similar issues).

Where to get php_perl.dll while pecl4win is down?

I need to call a Perl script from a PHP file, and I've gotten as far as know that I need the Perl class, and that it's in the php_perl.dll extension. I've also downloaded the php_perl package from PECL, but as you know, it's just the source and needs to be compiled. I don't work in C, so compiling it's not really an option -- I tried downloading Visual Studio Express but I still can't seem to make it happen.
So I really need php_perl.dll, but http://pecl4win.php.net/ext.php/php_perl.dll just tells me that "The pecl4win build box is temporarily out of service. We're preparing a new build system." Surely there must be SOMEWHERE else I can get the DLL, but I can't seem to find it. Every link I find seems to either be someone else looking for it, or a warez-looking site that wants you to give them your credit card info.
Thanks...
---- Nick
The Internet Archive Wayback Machine results look promising, perhaps one of the links will lead you to the file (although they often take such binary files out of the archive).
EDIT: I was able to get the DLL for the older branch php-5.0.5 (5_0) that way and uploaded it here (removed). Or try the direct link.
Looking for the newer branch php-5.1.6 (5_1) however gave no results so far, I checked the 4 most recent dates.
EDIT2: Found another working link for branch php-5.1.2.
The sidebar
says to use the following repository until the new buildsystem is online:
http://downloads.php.net/pierre/

Compiling PHP from source using Microsoft Visual c++ 2008 error

First off i want to thank everyone who has contributed towards making this website the great resource that it is today.
OK, Here is my problem.
I am trying to work with id3 tags in php and im using wamp server 2.0i on my vista 32bit ultimate. I followed the steps at php's wiki page on compiling extension for windows machines.(cant post the link).everything goes nice and smooth up until towards the end where i get an error saying fatal error c1083. could not open header zlib.h. I am running the shell as the administrator and not really sure what else there is i can do. But im really going crazy over this. I have followed instructions step by step but some how i am still getting stuck. Here is the link to the text file containing the compiling process.
https://docs.google.com/leaf?id=0Byjn3U-sXJBHNjA3ZTI1NTktYzlmZS00NjAxLTgyNzYtYTM3ZTRhYmY2NzE2&hl=en&authkey=CL6j7e4D
Thanks in advance,
I'm just gonna bang my head against the wall for little bit more and then either get unconscious or sleepy! LOL
Wooohoooo, Ok all I had to do was configure --disable-zlib and then nmake. But now one more thing. I am using wamp server and i tried just copy and pasting the produced folder but wamp does not like it and just crashes. Oops. good thing i kept the old copy of the php folder as a back up (unlike what i usually do). So i guess my question is: how do i use this compiled php with my id3 module? sorry about the dumm question.
The PECL id3 module is listed in alpha and hasn't been modified since 2004, so it is very unlikely that you'll be able to use it in any stable method against PHP 5.3.
Have you considered using the GPL-based getID3 class ( http://getid3.sourceforge.net/ ) which, despite its name, is capable of reading and writing id3 from a wide variety of files and has comparable functions to everything the id3 module ( http://us2.php.net/id3 ).

Joomla module works locally but displays nothing when hosted

I am new to joomla and I need to work on a joomla website for a school project. I modified an existing module to make it display featured projects and it does that flawlessly when I test the site locally. However, when I uploaded my files to the hosted copy of the website, the module will load but does not display anything. It just loads the title and the area for the php output but there is nothing returned by the script. Why would this be happening? I have joomla mostly figured out but I'm stumped when it comes to this problem.
As far as I can tell, all files related to this module have been copied over successfully and it is setup properly in the module manager. I turned on debugging mode on the hosted copy and got this message when trying to load another page with this module on it:
Parse error: syntax error, unexpected
T_STRING in
/home/content/s/r/s/srsgdmnet/html/components/com_rbids/rbids.html.php
on line 1
I looked at the file and I don't have a clue what it's talking about. Line one is just "<?php" which is fine. Is it just saying line 1 but actually referring to a problem elsewhere? This file is part of a reverse auctions component that my module interacts with. I didn't modify the code in that file with the exception of using a regular expression (search using "\n\s*(\n)", replace with "\n") to remove excessive amounts of whitespace via the replace command in Netbeans. This cut roughly 3200 lines from the file, making it much easier to navigate. I assume this did not alter anything in terms of code because it still works fine when used locally.
I modified my local configuration.php file to use the same database as the hosted copy to see if it was a database issue but it still worked fine so that rules that out. The php.ini files are the same on both copies with the exception of the local one having the Zend stuff commented out so I could use Xdebug (made this change after the problem occurred in an attempt to locate it). I have stepped through the code with Xdebug and haven't been able to track the issue down so I'm thinking it's a configuration problem.
My local copy also does not load certain modules (main menu, for one) and I can't navigate to some of the other pages, not sure if that is related. The code is the same for both copies yet each one has different results. Am I skipping vital steps for migrating the code?
I am using Joomla version 1.5.9. Please help!
Your question is ten days old, so perhaps you solved it already. But my suggestion would be to check the code for forward and back slashes. It might be that the code uses \ which works locally but fails on your server where it needs /. In Joomla extensions you can replace folder separations by DS, in the way of 'folder'.DS.'subfolder' instead of 'folder/subfolder'. The API will replace the DS by \ or / as appropriate.
However, the parse error you get indicates that something is missing in the syntax of your code. You will just have to go over it with a magnifyer glass. Sometimes when the error refers to the first line the impact of something missing works its way back to the beginning of the file. It could be a ' or ; or something small like that.
Regardless of your module, you should update to Joomla version 1.5.15 which at present is the latest version. you are 6 security releases behind schedule!
The group I have been working with has come to the conclusion that somehow Netbeans is messing up some of the files when we edit and save them. We tested by taking files from our server, opening and then saving in Netbeans, and then uploading back to the server. Sometimes this produced files that apparently did not have any newlines in them and led to php errors, breaking components or even taking down the whole site.
Our current workaround for this is to just take the files this happens to and use notepad++ to make our changes before uploading. It's a very strange issue and caused us a lot of grief. Hopefully the Netbeans team fixes this in future releases.
Thank you all for your attempts to help me solve this problem.
Try closing your <?php the traditional way and see if it works or the error line changes.
I remember seeing a similar question either on Joomla or Fabrik forums but cannot remember precise answer

Categories