ParkerAndKent saidI was suggesting to use something like
Yes, is what I do in my function I guess… because when you get the image url in a sub blog, the url returned is passed through rewrite rules, so it needs to be modified to point to the real sub blog uploads folder on server, otherwise scripts like timthumb fail.
$ud = wp_upload_dir(); $file = str_replace($ud["baseurl"],$ud["basedir"],$url);didn’t test at all but wp_upload_dir() would always provide right values whether multisite is enabled or not.
not sure if i got the problem but wouldn’t be simpler to just strip upload url from image and prepend upload dir to obtain file path ?
He means the URL posted by a buyer which points to his online page where he has installed the item he has just bought and is having a problem with. At the link the item’s unprotected sources are available for someone to take. As I’m sure you can understand, this is not such a nice thing to have in your file comments area.
Thanks for your interest. We’ve replied to your email.
Thanks to all for the applications, keep them coming, we’re going through them slowly, and will get back to everyone.
The pixelentity team is seeking a part time support staff member to join our team.
We are a 2-man team who are full time authors here on the Envato marketplaces. As our number of items for sale increase we are spending more and more time providing support to our buyers and less time creating new stuff. Consequently we are looking for someone to help out in our support forum in order to ease the load on us and allow us to concentrate more on development. This person would be working with buyers who have bought anything from our portfolio, which includes the following types of items:
- HTML5 Templates,
- WordPress Themes,
- jQuery Plugins and
- WordPress Plugins.
Support would be given via our external support forum, where a moderator role would be assigned. We would still be putting some time into support, especially in the comments area of our files, so the successful person would not be working alone. We are based in Central European Time (GMT +1) and though being located near this timezone would be good, it is not essential.
The right person will have all of the following:
- A good knowledge of PHP , Wordpress, Js, jQuery, CSS and HTML
- The patience of a saint and the ability to keep a cool head.
- A good command of the English language
- Experience of providing support for similar products
Initially we will be looking for someone for an average of 1-2 hours / day , during business days (Mon-Fri). We say an average because some days when there are no support queries, while other days there will be many. This daily requirement will very likely increase over time as our portfolio increases in size, so the right person would need to be open to increase this time commitment in the future.
If you are interested in applying for this role, please get in touch with us via our profile page. Include the following:
- A brief description of yourself,
- Details of your experience,
- Any relevant links,
- Your expected monthly salary for this position
just did a quick test and the upgrade worked nice and smooth. I was wondering if future updates of the library would hook into the standard WP upgrade system so that updates would be listed like themes/plugins downloaded from wp.org (Just to be more clear, i’m talking about update-core.php page)
Or will the library remain “low level” with each author integrating it in his/her own way ? Not trying to skip home work (well, maybe just a little bit) but wanted to avoid working on features that the library could offer itself in the future.
glad to know it, ok we’ll have a go then. Thanks
We’d like to include the auto-update feature in our framework but i see some bugs being reported here and no changes in git repo since 3 months now.
Is this project actively mantained ?
if you get the 404 page, problem is permalink structure not being updated (as pixelous pointed out). Either save the permalink page or call once flush_rewrite_rules() .
Ivor saidJust a question about theme check, we get a bunch of warnings about using “file_get_contents” ....
That said, Themes and Templates are rigorously tested. Just to give you an example, themes are tested with:
- WP_DEBUG enabled.
- Theme Check
- Log Deprecated Notices
would reviewers really enforce the above rule ? we have valid reasons to read a file in our theme folder like many other well known plugins. For instance, wordpress importer gets 3 warnings for using file_get_contents/fopen/fclose.
Giving reasons in the message to reviewer box would be enough ?